Re: listen_addresses = '*' ok, specific address(es) no (.... and a thread hi-jack!)

Dang - Our NZ operations are a lot smaller than ours. They only have the one
Linux server and it's primary role is to run the D3 gear I was talking about
the other day - same in Australia!! I am trying to get the number crunchers
to fork out the $$$ for RH ES4 and a nice new server.

Thanks Tom, I'll put up with the errors for now until I can get them a new
server.
-p


-----Original Message-----
From: Tom Lane [mailto:tgl@sss.pgh.pa.us]
Sent: Friday, 16 June 2006 1:04 PM
To: phillips@weatherbeeta.com.au
Cc: pgsql-sql@postgresql.org
Subject: Re: [SQL] listen_addresses = '*' ok, specific address(es) no (....
and a thread hi-jack!)

"Phillip Smith" <phillips@weatherbeeta.com.au> writes:
> <HIJACK>
> I've just installed Postgres 8.1 on RedHat 7.1

Uh ... *why*?  I wouldn't use RH 7.1 today any more than I'd use PG 7.1 ...

> and I'm getting the error:
> "2006-06-16 14:49:00 NZST @ []LOG:  could not create IPv6 socket: Address
> family not supported by protocol"

It seems you've got libc code that supports IPv6 even though your kernel
does not (else PG would not have been told that an IPv6 address was a
possible translation of "localhost").  PG copes with this but will issue
LOG messages complaining about it.  If you don't like the warnings, fix
your system so it's all on the same page about whether IPv6 is supported.
        regards, tom lane


*******************Confidentiality and Privilege Notice*******************

The material contained in this message is privileged and confidential to
the addressee.  If you are not the addressee indicated in this message or
responsible for delivery of the message to such person, you may not copy
or deliver this message to anyone, and you should destroy it and kindly
notify the sender by reply email.

Information in this message that does not relate to the official business
of Weatherbeeta must be treated as neither given nor endorsed by Weatherbeeta.
Weatherbeeta, its employees, contractors or associates shall not be liable
for direct, indirect or consequential loss arising from transmission of this
message or any attachments