Date: Sun, 22 Jun 2008 17:43:13 -0400
From: Robert Treat <xzilla@users.sourceforge.net>
Subject: Re: archives.postgresql.org not responding
In-reply-to: <3434.1214117107@sss.pgh.pa.us>
To: pgsql-www@postgresql.org
Cc: Tom Lane <tgl@sss.pgh.pa.us>, "Joshua D. Drake" <jd@commandprompt.com>,
	Stefan Kaltenbrunner <stefan@kaltenbrunner.cc>
Message-id: <200806221743.13537.xzilla@users.sourceforge.net>
MIME-version: 1.0
Content-type: text/plain; charset=iso-8859-15
Content-transfer-encoding: 7bit
Content-disposition: inline
References: <20946.1214071021@sss.pgh.pa.us>
	<485DEDD0.9030004@commandprompt.com> <3434.1214117107@sss.pgh.pa.us>
User-Agent: KMail/1.9.9

On Sunday 22 June 2008 02:45:07 Tom Lane wrote:
> "Joshua D. Drake" <jd@commandprompt.com> writes:
> > Stefan Kaltenbrunner wrote:
> >> Tom Lane wrote:
> >>> I've been seeing connection timeouts for the last little while ...
> >>
> >> AFAIK - currently there is maintainance work going on at the CMD hosting
> >> facility besides archives also search,planet and the buildfarm are down
> >> currently  ...
> >
> > Longer than expected, but everything should be up but buildfarm. I am
> > out of caffeine at this point but will look at buildfarm first thing in
> > the morning.
>
> Fully understand about lack of caffeine --- but if this was a planned
> service outage, some advance notice to pgsql-www would've been
> appropriate, no?  Or did I just miss it?
>

He sent notice to sysadmins, but not pgsql-www. I'm not sure what the policy 
is, but seems like it might be good to send these outage notices to a more 
public list as well. (For example, there is currently a notice from Marc 
about doing maintanance on mail.postgresql.org which I believe was supposed 
to happen last night, though we haven't recieved a followup mail yet)

-- 
Robert Treat
Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL