Re: tsearch parser inefficiency if text includes urls or emails - new version - Mailing list pgsql-hackers

From Kevin Grittner
Subject Re: tsearch parser inefficiency if text includes urls or emails - new version
Date
Msg-id 4B1E2D1F020000250002D1FC@gw.wicourts.gov
Whole thread Raw
In response to Re: tsearch parser inefficiency if text includes urls or emails - new version  (Andres Freund <andres@anarazel.de>)
Responses Re: tsearch parser inefficiency if text includes urls or emails - new version  (Greg Smith <greg@2ndquadrant.com>)
List 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 by date:

Previous
From: Andres Freund
Date:
Subject: Re: tsearch parser inefficiency if text includes urls or emails - new version
Next
From: Robert Haas
Date:
Subject: Re: Adding support for SE-Linux security