X-Original-To: pgsql-www-postgresql.org@postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id E2A669FA5E9; Wed, 6 Sep 2006 13:29:46 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 52550-10; Wed, 6 Sep 2006 13:29:38 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- X-Greylist: from auto-whitelisted by SQLgrey- X-Greylist: from auto-whitelisted by SQLgrey- Received: from davinci.ethosmedia.com (server227.ethosmedia.com [209.128.84.227]) by postgresql.org (Postfix) with ESMTP id 12C489F9F79; Wed, 6 Sep 2006 13:29:04 -0300 (ADT) X-EthosMedia-Virus-Scanned: no infections found Received: from [63.195.55.98] (account josh@agliodbs.com HELO spooky.sf.agliodbs.com) by davinci.ethosmedia.com (CommuniGate Pro SMTP 4.1.8) with ESMTP id 10079546; Wed, 06 Sep 2006 09:01:44 -0700 From: Josh Berkus Organization: PostgreSQL @ Sun To: pgsql-core@postgresql.org Subject: Re: [CORE] Finally, the end of a nightmare ... Date: Wed, 6 Sep 2006 08:58:49 -0700 User-Agent: KMail/1.8.2 Cc: "Marc G. Fournier" , Jan Wieck , pgsql-www@postgresql.org References: <20060906003541.E13992@ganymede.hub.org> <44FE57B2.6060806@Yahoo.com> <20060906075312.S13992@ganymede.hub.org> In-Reply-To: <20060906075312.S13992@ganymede.hub.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200609060858.50043.josh@agliodbs.com> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.164 tagged_above=0 required=5 tests=AWL, FORGED_RCVD_HELO X-Spam-Level: X-Archive-Number: 200609/22 X-Sequence-Number: 10600 Marc, > I think we are covered for most everything *except* gborg at this time ;( > And we all know gborg needs to be merged into pgfoundry :) I'm still getting intermittent DNS failures for mail.postgresql.org. > JoshB, do you know if pgfoundry is being duplicated over to that new > server in any way, just in case something does happen? Not on an active basis -- remember, there's the whole 32/64 bit thing. Let's re-rsync the files, and then set up some kind of daily DB copy. -- Josh Berkus PostgreSQL @ Sun San Francisco