Message-ID: <44F3A2CB.4050105@commandprompt.com>
Date: Mon, 28 Aug 2006 19:13:31 -0700
From: "Joshua D. Drake" <jd@commandprompt.com>
Organization: Command Prompt, Inc.
User-Agent: Thunderbird 1.5.0.5 (X11/20060728)
MIME-Version: 1.0
To: Tom Lane <tgl@sss.pgh.pa.us>
CC: Bruce Momjian <bruce@momjian.us>, aklaver@comcast.net,
	pgsql-www@postgresql.org
Subject: Re: Search out of sync
References: <200608290010.k7T0A4d01908@momjian.us>
	<44F38FF5.6060409@commandprompt.com>
	<22751.1156817302@sss.pgh.pa.us>
In-Reply-To: <22751.1156817302@sss.pgh.pa.us>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Tom Lane wrote:
> "Joshua D. Drake" <jd@commandprompt.com> writes:
>> Bruce Momjian wrote:
>>> I just tested "index bloat" and I can confirm that the second returned
>>> result is incorrect if you click on it.  Is anyone addressing this?
> 
>> No.
> 
> Why not?  The search index needs to be rebuilt following Marc's
> re-reconstruction of the archives.  It didn't take too long to do
> it after the first reconstruction, what's the holdup this time?

I have restarted the search engine daemons.

The hold up is simple:

1. Our search sucks.
2. I have zero idea how our search works beyond stop/start
3. Our search sucks.

Joshua D. Drake


> 
> 			regards, tom lane
> 


-- 

    === The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
    Providing the most comprehensive  PostgreSQL solutions since 1997
              http://www.commandprompt.com/