| From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, 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 18:06:55 |
| Message-ID: | 200309041806.h84I6tG04122@candle.pha.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom Lane wrote:
> Peter Eisentraut <peter_e(at)gmx(dot)net> 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?
>
> > 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.
>
> To what purpose? I think I prefer Andrew Dunstan's approach of allowing
> IPv4 syntax in pg_hba.conf to match appropriate IPv6 connections.
I am confused. Andrew Dunstan's approach added a new 'loopback' line
to pg_hba.conf.
Andreas Pflug had the patch that treated IPv4 as IPv6.
--
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2003-09-04 18:13:37 | Re: [HACKERS] Win32 native port |
| Previous Message | Patrick | 2003-09-04 18:06:16 | PostgreSQL port from DBExperts anybody using it ? |