Re: archives.postgresql.org not responding

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Marc G(dot) Fournier" <scrappy(at)hub(dot)org>
Cc: Robert Treat <xzilla(at)users(dot)sourceforge(dot)net>, pgsql-www(at)postgresql(dot)org, "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc>
Subject: Re: archives.postgresql.org not responding
Date: 2008-06-22 22:43:45
Message-ID: 29660.1214174625@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-www

"Marc G. Fournier" <scrappy(at)hub(dot)org> writes:
> If it involves web infrastructure (ie. archives.postgresql.org), it
> should go to pgsql-www ... if it involves non-web infrastructure
> (ie. ftp) it should go to sysadmins ...

Well, the point to me is that planned outages should be announced
somewhere where non-admins can see them. Which service is involved
shouldn't determine that.

regards, tom lane

In response to

Responses

Browse pgsql-www by date

  From Date Subject
Next Message Marc G. Fournier 2008-06-23 01:36:16 Mail VPS
Previous Message Joshua D. Drake 2008-06-22 22:22:20 Re: archives.postgresql.org not responding