Subject: Re: [GENERAL] List archives search function broken
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Date: Sun, 5 Dec 2004 21:51:32 +1100
Content-class: urn:content-classes:message
Message-ID: <5066E5A966339E42AA04BA10BA706AE56219@rodrick.geeknet.com.au>
Thread-Topic: [pgsql-www] [GENERAL] List archives search function broken
Thread-Index: AcTarqt95afBmsDVQWmXqKlnrGussgACPMww
From: "John Hansen" <john@geeknet.com.au>
To: "Oleg Bartunov" <oleg@sai.msu.su>, "Michael Fuhr" <mike@fuhr.org>
Cc: <pgsql-general@postgresql.org>, <pgsql-www@postgresql.org>

> > Using the list archive search function currently fails with
> > 503 Service Unavailable.
> >
> > Should messages about list archive problems go to pgsql-general, or=20
> > would it be better to use one of the other lists like bugs, hackers,

> > or www?
>=20
> I think complaints should go to -www list. btw, www.pgsql.ru=20
> is working and I think it could be as 'backstop' for main=20
> search engine, for example on "server error" there could link=20
> to http://www.pgsql.ru/db/pgsearch/index.html?set=3Darchives

Not a bad idea, but I won't be able to implement that, as the frontend
does not allow per virtual host error pages. - Unless someone is willing
to write a patch for pound (http://www.apsis.ch/pound).

Btw, this would have been caught earlier, if not for the fact that I've
been without an internet connection @ home for the past few days. Db
backend server OS had shut down for yet to be determined reasons.

Kind Regards,

John