Re: IPv6 patch

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Rocco Altier <RoccoA(at)Routescape(dot)com>, Nigel Kukard <nkukard(at)lbsd(dot)net>, Robert Treat <xzilla(at)users(dot)sourceforge(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: IPv6 patch
Date: 2003-01-07 21:09:34
Message-ID: 200301072109.h07L9Yn13061@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Peter Eisentraut wrote:
> Bruce Momjian writes:
>
> > Peter was the first to mention it. His reasoning was that if IPv6 was
> > working, but then stopped working, the admin would never know on startup
> > because of the IPv4 fallback.
>
> My view was that we should treat unix, ipv4, and ipv6 as independent
> address families each with their own on/off switch (except that unix
> doesn't have an off switch). Tom's view is that we should treat ipv4 and
> ipv6 as effectively one address family. That makes sense, too, and it is
> probably more with the spirit of IPv6.

OK, Peter, to keep you and everyone happy, what changes are your
proposing to the existing code, if any. The only current behavior is
printing an IPv6 failure for IPv6-enabled backend in the server logs.

--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Claiborne, Aldemaco Earl (Al) 2003-01-07 21:15:57 compiling postgres on windows: major headache
Previous Message Tom Lane 2003-01-07 21:08:33 Re: Read-only transactions