From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
---|---|
To: | Postgresql Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Bogus bind() warnings |
Date: | 2003-11-06 22:38:58 |
Message-ID: | 3FAACD82.9090105@dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane wrote:
>Kurt Roeckx <Q(at)ping(dot)be> writes:
>
>
>>Should we just not give that error message, in case we already
>>binded to AF_INET6 ::?
>>
>>
>
>Seems like a cure worse than the disease to me --- it could mask
>real problems. I suppose we could think about dropping it from LOG
>to DEBUG1 level, so that it wouldn't appear in a default setup;
>but I'm not sure I'm for that either.
>
>Given the, ahem, wide variety of behaviors that seem to be out there,
>I think we'd best be happy if we have a v4/v6 implementation that has
>no problems worse than spurious log messages ...
>
>
I agree. Things that might be serious problems should not be hidden.
Maybe it would be better to add a message that the error might be
harmless if you have IPv6 turned on.
cheers
andrew
From | Date | Subject | |
---|---|---|---|
Next Message | Gaetano Mendola | 2003-11-06 22:49:19 | Re: postgresql-7.4RC1 - Memory fault(coredump) on HP-UX |
Previous Message | Josh Berkus | 2003-11-06 22:33:25 | Re: [HACKERS] Changes to Contributor List |