Received: from magus.postgresql.org (magus.postgresql.org [87.238.57.229]) by mail.postgresql.org (Postfix) with ESMTP id DFF773F2E7B for ; Fri, 25 May 2012 18:18:28 -0300 (ADT) Received: from cronos.madness.at ([2a02:16a8:dc41::10]) by magus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1SY1tx-0002EF-Th for pgsql-www@postgresql.org; Fri, 25 May 2012 21:18:27 +0000 Received: from mastermind.kaltenbrunner.cc ([2001:470:7a2d::22]) by cronos.madness.at with esmtpsa (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.72) (envelope-from ) id 1SY1tf-0001Gt-Nb for pgsql-www@postgresql.org; Fri, 25 May 2012 23:18:09 +0200 Message-ID: <4FBFF70C.50309@kaltenbrunner.cc> Date: Fri, 25 May 2012 23:18:04 +0200 From: Stefan Kaltenbrunner User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.24) Gecko/20111120 Icedove/3.1.16 MIME-Version: 1.0 To: PostgreSQL www Subject: HEADSUP - {www,ftp}.postgresql.org IPv6 enabled X-Enigmail-Version: 1.1.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Pg-Spam-Score: -1.9 (-) X-Archive-Number: 201205/56 X-Sequence-Number: 20680 The postgresql.org sysadmin team has been working hard on ipv6 enabling our services in the past few months and we have just turned on IPv6 for www.postgresql.org and ftp.postgresql.org (a fair number of services had been ipv6 before) so this is mostly a headsup because those are really end-user visible services and prone to odd issues... Feedback in either direction (works great or breaks everything) is very much appreciated but in general we expect people to not notice any operational impact at all... regards Stefa