Tom Lane wrote:
Andrew Dunstan <[EMAIL PROTECTED]> writes:
Try this instead if you prefer.
I thought this was a little bit too trusting about there being a
getaddrinfo to probe, so I tightened it up as per the attached
applied patch.
Where are we at this point on the Windows/IPv6 i
Andrew Dunstan <[EMAIL PROTECTED]> writes:
> Try this instead if you prefer.
I thought this was a little bit too trusting about there being a
getaddrinfo to probe, so I tightened it up as per the attached
applied patch.
Where are we at this point on the Windows/IPv6 issue --- are there
more fixes
Tom Lane wrote:
Andrew Dunstan <[EMAIL PROTECTED]> writes:
Tom Lane wrote:
If you like, you can improve initdb to comment that line out if
getaddrinfo chokes on "::1", rather than believing HAVE_IPV6.
Good idea. Here's a patch for that. Rather than commenting it out I use
Andrew Dunstan <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> If you like, you can improve initdb to comment that line out if
>> getaddrinfo chokes on "::1", rather than believing HAVE_IPV6.
> Good idea. Here's a patch for that. Rather than commenting it out I used
> the slightly newer initdb f
Tom Lane wrote:
Andrew Dunstan <[EMAIL PROTECTED]> writes:
The one place that very slightly bothers me is the ::1 line in
pg_hba.conf. The fact that it comes last in the default config is its
saving grace - it won't ever be reached by a passing connection. I think
at least, though, we s
