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

From Tom Lane
Subject Re: tsearch parser inefficiency if text includes urls or emails - new version
Date
Msg-id 27017.1260301392@sss.pgh.pa.us
Whole thread Raw
In response to Re: tsearch parser inefficiency if text includes urls or emails - new version  (Greg Smith <greg@2ndquadrant.com>)
Responses Re: tsearch parser inefficiency if text includes urls or emails - new version  (Greg Smith <greg@2ndquadrant.com>)
Re: tsearch parser inefficiency if text includes urls or emails - new version  ("Kevin Grittner" <Kevin.Grittner@wicourts.gov>)
List pgsql-hackers
Greg Smith <greg@2ndquadrant.com> writes:
> Kevin Grittner wrote:
>> Anyway, I'm not sure whether your reply directly answers the point
>> I was raising -- peg doesn't do anything with the compiler
>> optimization flags under the covers, does it?
>> 
> Not really.  It does this:

> PGDEBUG="--enable-cassert --enable-debug"
> ./configure --prefix=$PGINST/$PGPROJECT --enable-depend 
> --enable-thread-safety $PGDEBUG

--enable-cassert might have a noticeable performance impact.
We usually try to not have that on when doing performance testing.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Greg Smith
Date:
Subject: Re: More broken links in documentation
Next
From: Magnus Hagander
Date:
Subject: Re: More broken links in documentation