Re: tsearch parser inefficiency if text includes urls or emails - new version
От | Kevin Grittner |
---|---|
Тема | Re: tsearch parser inefficiency if text includes urls or emails - new version |
Дата | |
Msg-id | 4B1E2D1F020000250002D1FC@gw.wicourts.gov обсуждение исходный текст |
Ответ на | Re: tsearch parser inefficiency if text includes urls or emails - new version (Andres Freund <andres@anarazel.de>) |
Ответы |
Re: tsearch parser inefficiency if text includes urls
or emails - new version
|
Список | pgsql-hackers |
Andres Freund <andres@anarazel.de> wrote: > Did you test that with a optimized build? After running a series of tests with --enable-cassert to confirm that nothing squawked, I disabled that before doing any performance testing. Going from memory, I used --enable-debug --with-libxml and --prefix. I didn't explicitly use or disable any compiler optimizations. Possibly relevant is that I was using Greg Smith's peg tool (as best I could): http://github.com/gregs1104/peg/ I'm not aware of it doing anything to the compile options, but I didn't look for that, either. I guess I should poke around that some more to be sure. After having peg do the checkout and set up the directories, did my own ./configure and make runs so that I could be sure of my configure settings. Are there any settings which you feel I should be using which PostgreSQL doesn't set up as you would recommend during the ./configure run? -Kevin
В списке pgsql-hackers по дате отправления: