Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: archives.postgresql.org not responding
- From: Bruce Momjian <bruce(at)momjian(dot)us>
- To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
- Cc: "Marc G. Fournier" <scrappy(at)hub(dot)org>, Robert Treat <xzilla(at)users(dot)sourceforge(dot)net>, pgsql-www(at)postgresql(dot)org, "Joshua D. Drake" <jd(at)commandprompt(dot)com>, Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc>
- Subject: Re: archives.postgresql.org not responding
- Date: Sun, 22 Jun 2008 21:48:57 -0400 (EDT)
- Message-id: <200806230148.m5N1mve23872@momjian.us> <text/plain>
Tom Lane wrote: > "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. Agreed. There should be a join-able list that will tell us about such things. I can't join sysadmins to find out about outages, and www seems to fit that role fine. -- Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us EnterpriseDB http://enterprisedb.com + If your life is a hard drive, Christ can be your backup. +
- References:
- Re: archives.postgresql.org not responding
- From: Tom Lane
- Re: archives.postgresql.org not responding
- Prev by Date: Mail VPS
- Next by Date: Revised downloads section on the website
- Previous by thread: Re: archives.postgresql.org not responding
- Next by thread: Mail VPS
- Indexes: