Re: TCP/IP with 7.4 beta2 broken? - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: TCP/IP with 7.4 beta2 broken?
Date
Msg-id Pine.LNX.4.44.0309041915430.1488-100000@peter.localdomain
Whole thread Raw
In response to Re: TCP/IP with 7.4 beta2 broken?  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: TCP/IP with 7.4 beta2 broken?  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: TCP/IP with 7.4 beta2 broken?  (Kurt Roeckx <Q@ping.be>)
Re: TCP/IP with 7.4 beta2 broken?  (Andrew Dunstan <andrew@dunslane.net>)
List pgsql-hackers
Tom Lane writes:

> Bruce Momjian <pgman@candle.pha.pa.us> writes:
> > Can we allow the IPv6 entries to be in pg_hba.conf but ignore them on
> > non-IPv6 machines, or allow the connection to fail?
>
> I don't see a good way yet.  The fly in the ointment is that HAVE_IPV6
> is set by configure based on the capabilities of userland libraries;
> we cannot assume that HAVE_IPV6 means the kernel knows IPv6.  But if
> we simply suppress failure messages on IPv6 addresses, we are going to
> create severe headaches for people who are actually using IPv6.

What is the problem?  Is it that a non-IPv6 enabled postmaster is unable
to identify or parse valid IPv6 address specifications?  In that case,
we need to provide some substitute routines.

-- 
Peter Eisentraut   peter_e@gmx.net



pgsql-hackers by date:

Previous
From: Kurt Roeckx
Date:
Subject: Re: compile warnings in CVS HEAD?
Next
From: Peter Eisentraut
Date:
Subject: Re: Win32 native port