Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 577A92E003B for ; Sat, 22 Mar 2008 13:01:53 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 30906-03 for ; Sat, 22 Mar 2008 13:01:50 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from lists.commandprompt.com (host-159.commandprompt.net [207.173.203.159]) by postgresql.org (Postfix) with ESMTP id 59BA42E0035 for ; Sat, 22 Mar 2008 13:01:50 -0300 (ADT) Received: from jd-laptop (or-69-34-217-90.sta.embarqhsd.net [69.34.217.90]) (authenticated bits=0) by lists.commandprompt.com (8.13.8/8.13.8) with ESMTP id m2MG2Dpj012318 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 22 Mar 2008 09:02:14 -0700 Date: Sat, 22 Mar 2008 09:01:41 -0700 From: "Joshua D. Drake" To: "Dave Page" Cc: "Bruce Momjian" , "Robert Treat" , pgsql-www@postgresql.org Subject: Re: Time to get infrastructure team-based Message-ID: <20080322090141.3584120a@jd-laptop> In-Reply-To: <937d27e10803220741k168e5873oca11029e852667a0@mail.gmail.com> References: <937d27e10803220732r61624e4bx4e7944aec3d6c8ce@mail.gmail.com> <200803221437.m2MEb1l27539@momjian.us> <937d27e10803220741k168e5873oca11029e852667a0@mail.gmail.com> Organization: Joshua D. Drake X-Mailer: Claws Mail 3.3.1 (GTK+ 2.12.0; i486-pc-linux-gnu) Mime-Version: 1.0 Content-Type: multipart/signed; boundary="Sig_/rG+m1ZO9VdT0EULy1VMXaUR"; protocol="application/pgp-signature"; micalg=PGP-SHA1 X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (lists.commandprompt.com [207.173.203.159]); Sat, 22 Mar 2008 09:02:14 -0700 (PDT) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200803/481 X-Sequence-Number: 14600 --Sig_/rG+m1ZO9VdT0EULy1VMXaUR Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable On Sat, 22 Mar 2008 14:41:05 +0000 "Dave Page" wrote: > > No, but it seems like a waste of time to even try. > > > > One idea is to set up the duplicate infrastructure with a domain in > > place, and if the domain change gets blocked, we just switch to > > the new domain name. >=20 > I don't even want to think about the ramifications of doing that. It would be ugly. Joshua D. Drake --=20 The PostgreSQL Company since 1997: http://www.commandprompt.com/=20 PostgreSQL Community Conference: http://www.postgresqlconference.org/ Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate PostgreSQL SPI Liaison | SPI Director | PostgreSQL political pundit --Sig_/rG+m1ZO9VdT0EULy1VMXaUR Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFH5S1lATb/zqfZUUQRAsGeAKCr84FSi8f6R0NWp9yOTDm5ZPSCYwCdHbBj acR+rX0hDHFmzO3TwGQje40= =7nZc -----END PGP SIGNATURE----- --Sig_/rG+m1ZO9VdT0EULy1VMXaUR--