| From: | <Charles(dot)McDevitt(at)emc(dot)com> |
|---|---|
| To: | <peter_e(at)gmx(dot)net>, <magnus(at)hagander(dot)net> |
| Cc: | <tgl(at)sss(dot)pgh(dot)pa(dot)us>, <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: non-ipv6 vs hostnames |
| Date: | 2011-08-17 17:12:45 |
| Message-ID: | 72AE4C5076364440BADFFCCB0A60785B08F651AC@MX02A.corp.emc.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> On tis, 2011-08-16 at 16:17 +0200, Magnus Hagander wrote:
> > Well, I got this on a win64 build. It's *supposed* to have ipv6. I
> > wonder if it breaks on windows just because there is no ipv6 address
> > on the machine...
>
> It would mean that getaddrinfo() of "::1" failed. That seems weird.
>
A system admin can set registry keys to disable IPv6, either partially (allowing ::1), or totally (all IPv6 addresses fail).
If the system has IPv6 enabled, it's not possible for there to be no ipv6 address. There is always the link-local address of each LAN adapter.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2011-08-17 17:20:32 | Re: PATCH: Compiling PostgreSQL using ActiveState Python 3.2 |
| Previous Message | Tom Lane | 2011-08-17 17:10:55 | Re: A note about hash-based catcache invalidations |