Re: TCP/IP with 7.4 beta2 broken?

From: Kurt Roeckx <Q(at)ping(dot)be>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Andreas Pflug <pgadmin(at)pse-consulting(dot)de>, Tommi Mäkitalo <t(dot)maekitalo(at)epgmbh(dot)de>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: TCP/IP with 7.4 beta2 broken?
Date: 2003-09-04 17:32:11
Message-ID: 20030904173211.GC14879@ping.be
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Sep 04, 2003 at 07:18:57PM +0200, Peter Eisentraut wrote:
> Tom Lane writes:
>
> > Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)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.

Our replacement getaddrinfo can only read IPv4 addresses.

If we need to make it support IPv6 addresses too, we need to
define our own struct sockaddr_in6 and AF_INET6, and always use
our own version and not the one from the system libs if it has
any.

There probably is no need for our getaddrinfo replacement
function to try to resolve to IPv6 addresses, so it shouldn't be
that hard.

Kurt

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Marc G. Fournier 2003-09-04 17:44:07 Re: ANONCVS? Is it being updated correctly?
Previous Message Tom Lane 2003-09-04 17:25:36 Re: TCP/IP with 7.4 beta2 broken?