| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | 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:25:36 |
| Message-ID: | 7985.1062696336@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kurt Roeckx | 2003-09-04 17:32:11 | Re: TCP/IP with 7.4 beta2 broken? |
| Previous Message | Kurt Roeckx | 2003-09-04 17:21:14 | Re: Stats Collector Error 7.4beta1 and 7.4beta2 |