Thread: Fwd: Re: Possible psql bug
This mail didn't make it to the list, it seems. Kurt On Thu, Jul 10, 2003 at 10:35:04AM +0800, Christopher Kings-Lynne wrote: > When I run psql on freebsd/alpha with latest CVS and no postmaster running, > I get this: > > bash-2.03$ psql test > psql: could not connect to server: No such file or directory > Is the server running locally and accepting > connections on Unix domain socket "ùÿÿÿÿÿÿÿØ`"? This is probably getnameinfo() not supporting AF_UNIX, which I already was afraid of. And the return value of getnameinfo() isn't checked either. My suggestion was to make our own getnameinfo_unix() like we have a getaddrinfo_unix() for exactly the same reason. It should be rather easy to write since we already have a getnameinfo() in it that supports it. Kurt
Kurt Roeckx <Q@ping.be> writes:
> On Thu, Jul 10, 2003 at 10:35:04AM +0800, Christopher Kings-Lynne wrote:
>> bash-2.03$ psql test
>> psql: could not connect to server: No such file or directory
>> Is the server running locally and accepting
>> connections on Unix domain socket "���������`"?
> This is probably getnameinfo() not supporting AF_UNIX, which I
> already was afraid of. And the return value of getnameinfo()
> isn't checked either.
You are right --- I have just checked this on Chris' system, and that's
exactly what happens.
> My suggestion was to make our own getnameinfo_unix() like we have
> a getaddrinfo_unix() for exactly the same reason.
Right, and a getnameinfo2() that wraps that in the same way getaddrinfo2()
does. Can you make this happen? I'm a bit swamped ...
regards, tom lane
On Wed, Jul 23, 2003 at 12:23:38PM -0400, Tom Lane wrote: > > > My suggestion was to make our own getnameinfo_unix() like we have > > a getaddrinfo_unix() for exactly the same reason. > > Right, and a getnameinfo2() that wraps that in the same way getaddrinfo2() > does. Can you make this happen? I'm a bit swamped ... I really have no time left. Leaving on holidays on Friday and still have lots of other things to do. Kurt