Thread: Search out of sync
I am seeing the same behavior as reported in the message below. http://archives.postgresql.org/pgsql-www/2006-08/msg00105.php Is there a fix in the works? Thank you, -- Adrian Klaver aklaver@comcast.net
Adrian Klaver wrote: > I am seeing the same behavior as reported in the message below. > http://archives.postgresql.org/pgsql-www/2006-08/msg00105.php > > Is there a fix in the works? 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? -- Bruce Momjian bruce@momjian.us EnterpriseDB http://www.enterprisedb.com + If your life is a hard drive, Christ can be your backup. +
Bruce Momjian wrote: > Adrian Klaver wrote: >> I am seeing the same behavior as reported in the message below. >> http://archives.postgresql.org/pgsql-www/2006-08/msg00105.php >> >> Is there a fix in the works? > > 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. Sincerely, Joshua D. Drake -- === 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/
"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?
regards, tom lane
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/
"Joshua D. Drake" <jd@commandprompt.com> writes:
> I am willing to put man and money resources behind our search engine, if
> I felt that our search engine was going to be productive :) but I never,
> ever use it.
It works well for me and for a lot of other people (at least when the
data is up-to-date). If you can't be bothered to maintain it, however,
I guess we need to find another host.
Any volunteers out there?
regards, tom lane
> It works well for me and for a lot of other people (at least when the
> data is up-to-date). If you can't be bothered to maintain it, however,
> I guess we need to find another host.
I guess it depends on what you are looking for, but it rarely works for me.
>
> Any volunteers out there?
Uhh, who said I was ever the maintainer? I am the host and have never
claimed to be maintainer. I am not the only one that has root on that
machine to help maintain that box. Dave Page, Applejack and Devrim all
have root on this machine.
Please see my next post on this thread.
Sincerely,
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/
Tom Lane wrote:
> "Joshua D. Drake" <jd@commandprompt.com> writes:
>> I am willing to put man and money resources behind our search engine, if
>> I felt that our search engine was going to be productive :) but I never,
>> ever use it.
/me digs around in the install and finds a suspicious scripts called:
update-archives
Reading the script, it updates some date statistics in the database
which appears to in theory cause the indexer to re-fire against
archives, pgfoundry and gborg..
So time will tell. Where is that wiki so I can document this, since I am
spending my time on it, I might as well make sure someone can come
behind me.
Sincerely,
Joshua D. Drake
--
=== 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/
Index resync started, no new messages will be indexed until it's finished. I missed the email about the archives was regenerated, and have spent hours trying to work out what had happened. This problem would have resolved itself tho, as the archives are reindexed every 30 days anyways. Kind regards, John > -----Original Message----- > From: pgsql-www-owner@postgresql.org > [mailto:pgsql-www-owner@postgresql.org] On Behalf Of Bruce Momjian > Sent: Tuesday, August 29, 2006 10:10 AM > To: aklaver@comcast.net > Cc: pgsql-www@postgresql.org > Subject: Re: [pgsql-www] Search out of sync > > Adrian Klaver wrote: > > I am seeing the same behavior as reported in the message below. > > http://archives.postgresql.org/pgsql-www/2006-08/msg00105.php > > > > Is there a fix in the works? > > 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? > > -- > Bruce Momjian bruce@momjian.us > EnterpriseDB http://www.enterprisedb.com > > + If your life is a hard drive, Christ can be your backup. + > > ---------------------------(end of > broadcast)--------------------------- > TIP 3: Have you checked our extensive FAQ? > > http://www.postgresql.org/docs/faq >
> -----Original Message----- > From: pgsql-www-owner@postgresql.org > [mailto:pgsql-www-owner@postgresql.org] On Behalf Of Joshua D. Drake > Sent: 29 August 2006 03:30 > To: Tom Lane > Cc: Bruce Momjian; aklaver@comcast.net; pgsql-www@postgresql.org > Subject: Re: [pgsql-www] Search out of sync > > > > It works well for me and for a lot of other people (at > least when the > > data is up-to-date). If you can't be bothered to maintain > it, however, > > I guess we need to find another host. > > I guess it depends on what you are looking for, but it rarely > works for me. Works well for me <shrug>. > > Any volunteers out there? > > Uhh, who said I was ever the maintainer? I am the host and have never > claimed to be maintainer. I am not the only one that has root on that > machine to help maintain that box. Dave Page, Applejack and > Devrim all > have root on this machine. Unfortunately I've been on holiday. And doesn't Devrim work for you? :-) /D
Hello, On Tue, 2006-08-29 at 08:35 +0100, Dave Page wrote: > Unfortunately I've been on holiday. And doesn't Devrim work for > you? :-) Do we have a text about how search engine works? I have zero idea about that. ... and having root does not mean that I know a lot about the search engine :-) Regards, -- The PostgreSQL Company - Command Prompt, Inc. 1.503.667.4564 PostgreSQL Replication, Consulting, Custom Development, 24x7 support Managed Services, Shared and Dedicated Hosting Co-Authors: plPHP, plPerlNG - http://www.commandprompt.com/
Attachment
>>> Any volunteers out there?
>> Uhh, who said I was ever the maintainer? I am the host and have never
>> claimed to be maintainer. I am not the only one that has root on that
>> machine to help maintain that box. Dave Page, Applejack and
>> Devrim all
>> have root on this machine.
>
> Unfortunately I've been on holiday. And doesn't Devrim work for you? :-)
Yes, Devrim works for me :)
Joshua D. Drake
>
> /D
>
--
=== 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/
John Hansen wrote: > Index resync started, no new messages will be indexed until it's > finished. > > I missed the email about the archives was regenerated, and have spent > hours trying to work out what had happened. > > This problem would have resolved itself tho, as the archives are > reindexed every 30 days anyways. It still does not work. If you search "index bloat", the second item is "Constraints" and there is no mention of index bloat there. Before the reindex, the second item said index bloat, but pointed to the "Constraints" email. Could this be caused by Marc fixing the indexes based on pre-post July 2006 indexing needs. -- Bruce Momjian bruce@momjian.us EnterpriseDB http://www.enterprisedb.com + If your life is a hard drive, Christ can be your backup. +
Bruce Momjian Wrote: > It still does not work. If you search "index bloat", the > second item is "Constraints" and there is no mention of index > bloat there. Before the reindex, the second item said index > bloat, but pointed to the "Constraints" email. Could this be > caused by Marc fixing the indexes based on pre-post July 2006 > indexing needs. No, the archives are being reindexed, and the indexer is still running. While it's running, results will be somewhat screwed, until the reverse index is updated, which doesn't occur till it's beenthru all of the pages. (some 500.000+ of them) Be patient please. Kind Regards, John
Bruce Momjian wrote: > John Hansen wrote: >> Index resync started, no new messages will be indexed until it's >> finished. >> >> I missed the email about the archives was regenerated, and have spent >> hours trying to work out what had happened. >> >> This problem would have resolved itself tho, as the archives are >> reindexed every 30 days anyways. > > It still does not work. If you search "index bloat", the second item is > "Constraints" and there is no mention of index bloat there. Before the > reindex, the second item said index bloat, but pointed to the > "Constraints" email. Could this be caused by Marc fixing the indexes > based on pre-post July 2006 indexing needs. Who knows :). I have no idea why the constraints email would show up at all frankly. Sincerely, Joshua D. Drake > > -- > Bruce Momjian bruce@momjian.us > EnterpriseDB http://www.enterprisedb.com > > + If your life is a hard drive, Christ can be your backup. + > > ---------------------------(end of broadcast)--------------------------- > TIP 9: In versions below 8.0, the planner will ignore your desire to > choose an index scan if your joining column's datatypes do not > match > -- === 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/
Search is now in sync. ... John
John Hansen wrote: > Search is now in sync. Yes, I can confirm. Thanks for the fix. -- Bruce Momjian bruce@momjian.us EnterpriseDB http://www.enterprisedb.com + If your life is a hard drive, Christ can be your backup. +