Re: IPv6 patch

From: "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au>
To: "Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)us>, "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-28 01:18:14
Message-ID: GNELIHDDFBOCMGBFGEFOIEDECFAA.chriskl@familyhealth.com.au
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> > > However, the server log messages stating an IPv6 socket was
> not made is
> > > only printed if the binary supports IPv6. The message seems to be a
> > > compromise between those who wanted a separate IPv6 GUC/flag and those
> > > who wanted it to silently fail on IPv6.
> >
> > I'm not sure. Those who wanted silence don't get any silence and those
> > who wanted a configurable hard failure get neither the
> configurability nor
> > any failure.
>
> That is the compromise. Neither gets what they want, but the final
> solution is closer to each. This is probably the best we can do.

BTW guys, there was strong demand at Linux.conf.au asking for the 'inet'
type to support IPv6 addresses. I've been looking at it a bit, but I'll
have to interleave it with my work on phpPgAdmin 3 (which rocks BTW :) ).

Chris

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2003-01-28 01:19:35 Re: IPv6 patch
Previous Message Bruce Momjian 2003-01-27 23:58:05 Fix for log_min_error_messages