> -----Original Message-----
> From: Tom Lane [mailto:tgl@sss.pgh.pa.us]
> Sent: 19 May 2004 19:34
> To: Jeffrey W. Baker
> Cc: pgsql-hackers@postgresql.org; Marc Fournier
> Subject: [HACKERS] search engine down (again)
>
> "Jeffrey W. Baker" <jwbaker@acm.org> writes:
> > If you are referring to archives.postgresql.org, all I have
> to say is:
> > "An error occured! Can not connect to search daemon"
> > And as far as I have seen, it's been like that for years.
>
> I do seem to be getting that today (Marc?) but it's hardly
> been "like that for years".
We've (well, mainly John) have been trying to track down a *very*
elusive bug in the thread timeout code the clears idle search threads
from the pool. On odd occasions it can shutdown all listening threads
hence the 'cannot connect' message. Unfortunately, it often runs for a
few weeks before dying. If anyone wants to look over the code (C++) to
see what we missed they'd be more than welcome. Just let me know.
In this case though, that wasn't the problem and unfortunately I had to
wait for Marc to wake up before I could do anything further with it.
Should be OK now though :-)
Regards, Dave.
