Re: tsearch parser inefficiency if text includes urls or emails - new version

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: "Andres Freund" <andres(at)anarazel(dot)de>
Cc: <greg(at)2ndquadrant(dot)com>,<pgsql-hackers(at)postgresql(dot)org>, <oleg(at)sai(dot)msu(dot)su>, <teodor(at)sigaev(dot)ru>
Subject: Re: tsearch parser inefficiency if text includes urls or emails - new version
Date: 2009-12-08 16:40:31
Message-ID: 4B1E2D1F020000250002D1FC@gw.wicourts.gov
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Andres Freund <andres(at)anarazel(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2009-12-08 16:48:07 Re: Adding support for SE-Linux security
Previous Message Andres Freund 2009-12-08 16:17:19 Re: tsearch parser inefficiency if text includes urls or emails - new version