The large print giveth and the small print taketh away - Tom Waits
On Tue, Nov 21, 2006 at 10:34:28PM +0100, Magnus Hagander wrote:
I intended to read a thread I caught part of in Oct, so I went to the
archive: http://archives.postgresql.org/pgsql-general/
Seems most of the months
On Sat, 4 Dec 2004, Michael Fuhr wrote:
Using the list archive search function currently fails with
503 Service Unavailable.
Should messages about list archive problems go to pgsql-general,
or would it be better to use one of the other lists like bugs,
hackers, or www?
I think complaints should go
Using the list archive search function currently fails with
503 Service Unavailable.
Should messages about list archive problems go to pgsql-general, or
would it be better to use one of the other lists like bugs, hackers,
or www?
I think complaints should go to -www list. btw,
John,
you could always rely on your script where you check if db handler is
alive and if not then show gentle error message with link to www.pgsql.ru
Oleg
On Sun, 5 Dec 2004, John Hansen wrote:
Using the list archive search function currently fails with
503 Service Unavailable.
Should
John,
you could always rely on your script where you check if db
handler is alive and if not then show gentle error message
with link to www.pgsql.ru
I never check if dbhandler is alive in the frontend
This was the backend OS that shut down, which also hosts the filesystems
for the
Using the list archive search function currently fails with
503 Service Unavailable.
Should messages about list archive problems go to pgsql-general,
or would it be better to use one of the other lists like bugs,
hackers, or www?
--
Michael Fuhr
http://www.fuhr.org/~mfuhr/
fixed
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Michael Fuhr
Sent: Sunday, December 05, 2004 9:41 AM
To: [EMAIL PROTECTED]
Subject: [GENERAL] List archives search function broken
Using the list archive search function currently fails
The list archives at http://archives.postgresql.org/ don't appear
to have been updated since Tue 30 Nov. Is something amiss?
--
Michael Fuhr
http://www.fuhr.org/~mfuhr/
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please
Joshua? Everything looks fine on the main server itself ... and John
grab'd his update this morning around 3am, so rsyncd on our side is
working as well ... problems on your end?
On Thu, 2 Dec 2004, Michael Fuhr wrote:
The list archives at http://archives.postgresql.org/ don't appear
to have
Marc G. Fournier [EMAIL PROTECTED] writes:
Joshua? Everything looks fine on the main server itself ... and John
grab'd his update this morning around 3am, so rsyncd on our side is
working as well ... problems on your end?
It looks like the issue is that the toplevel web pages haven't had a
On Thu, 2 Dec 2004, Tom Lane wrote:
Marc G. Fournier [EMAIL PROTECTED] writes:
Joshua? Everything looks fine on the main server itself ... and John
grab'd his update this morning around 3am, so rsyncd on our side is
working as well ... problems on your end?
It looks like the issue is that the
Marc G. Fournier wrote:
Joshua?
Taking a look now. Looks like we are having a minor DNS issue which is
causing the DNS lookup to srv5 to fail.
Sincerely,
Joshua D. Drake
Everything looks fine on the main server itself ... and John
grab'd his update this morning around 3am, so rsyncd on our
Joshua D. Drake wrote:
Marc G. Fournier wrote:
Joshua?
Taking a look now. Looks like we are having a minor DNS issue which is
causing the DNS lookup to srv5 to fail.
Sincerely,
Joshua D. Drake
Everything looks fine on the main server itself ... and John
grab'd his update this morning around
On Thu, 2 Dec 2004, Michael Fuhr wrote:
The list archives at http://archives.postgresql.org/ don't appear
to have been updated since Tue 30 Nov. Is something amiss?
Fix.
--
Michael Fuhr
http://www.fuhr.org/~mfuhr/
---(end of
broadcast)---
TIP 3:
On Thu, 2 Dec 2004, Joshua D. Drake wrote:
Marc G. Fournier wrote:
Joshua?
Taking a look now. Looks like we are having a minor DNS issue which is
causing the DNS lookup to srv5 to fail.
'k, let me know how it goes ... just checked UUnet's name server:
# nslookup svr5.postgresql.org ns.uunet.ca
'k, let me know how it goes ... just checked UUnet's name server:
# nslookup svr5.postgresql.org ns.uunet.ca
Server: ns.uunet.ca
Address: 142.77.1.1
Name:svr5.postgresql.org
Address: 66.98.251.16
and it resolves fine :(
Yeah it is definately a local issue here.
Sincerely,
Joshua D. Drake
On Thu, 2 Dec 2004, Joshua D. Drake wrote:
Joshua D. Drake wrote:
Marc G. Fournier wrote:
Joshua?
Taking a look now. Looks like we are having a minor DNS issue which is
causing the DNS lookup to srv5 to fail.
Sincerely,
Joshua D. Drake
Everything looks fine on the main server itself ... and
Finally figuring that enough is enough, I've been spending the past few
days working on the list archives ...
I've reformatted, so far, the following lists into a cleaner format:
pgsql-hackers
pgsql-sql
pgsql-bugs
pgsql-general
pgadmin-hackers
18 matches
Mail list logo
