On 09/11/12 12:55 PM, Merlin Moncure wrote:
is their any chance this will ever be addressed?
have you got your aix completely up to date with all patches? I got
burned in a similar fashion a while back on a related call --
getaddrinfo IIRC.
It was updated to 'current' a year or so ago, I beli
On Tue, Sep 11, 2012 at 11:09 AM, John R Pierce wrote:
> we're still having issues with PG on AIX 6.1, our configurations have no
> ipv6 as our WAN is purely ipv4, but if we use listen_addresses='*', we
> consistently get an error...
>
> LOG: could not bind IPv6 socket: Address already in use
On Tue, Sep 11, 2012 at 09:09:22AM -0700, John R Pierce wrote:
>
> is their any chance this will ever be addressed?
The problem you're having is that "*" means "bind to all the addresses
on this machine", and for some reason IBM's strange and wonderful
implementation of the IP layer appears to gi
On 09/11/12 10:12 AM, Adrian Klaver wrote:
Did not say what version you where on. But in 9.1:
http://www.postgresql.org/docs/9.1/interactive/runtime-config-connection.html
"The special entry * corresponds to all available IP interfaces. The entry
0.0.0.0
allows listening for all IPv4 addresses
On 09/11/2012 09:09 AM, John R Pierce wrote:
> we're still having issues with PG on AIX 6.1, our configurations have no
> ipv6 as our WAN is purely ipv4, but if we use listen_addresses='*', we
> consistently get an error...
>
> LOG: could not bind IPv6 socket: Address already in use
>
>
John R Pierce writes:
> we're still having issues with PG on AIX 6.1, our configurations have no
> ipv6 as our WAN is purely ipv4, but if we use listen_addresses='*', we
> consistently get an error...
> LOG: could not bind IPv6 socket: Address already in use
This was discussed at bug #649
we're still having issues with PG on AIX 6.1, our configurations have no
ipv6 as our WAN is purely ipv4, but if we use listen_addresses='*', we
consistently get an error...
LOG: could not bind IPv6 socket: Address already in use
the workaround we've been using is to set listen_addresses
