we spent quite a lot of effort to diagnose what turned out to be a simple
networking misconfiguration. It would probably have taken a lot less
effort if the postmaster were more forthcoming about exactly what address
it's trying to bind to. I seem to recall having wanted to include that
info in the messages many years ago, but at the time we lacked any
reasonably-portable way to decode a struct addrinfo. Now we have
pg_getnameinfo_all(), so PFA a patch to include the specific address in
any complaint about failures in the socket/bind/listen sequence.
For good measure I also added a DEBUG1 log message reporting successful
binding to a port. I'm not sure if there's an argument for putting this
out at LOG level (i.e. by default) --- any thoughts about that?
There are probably a couple of example messages in the SGML docs that
would need to be updated, but I've not trawled for them yet.
regards, tom lane
pgsql-hackers by date
|Next:||From: Peter Eisentraut||Date: 2017-03-09 20:34:30|
|Subject: Re: cast result of copyNode()|
|Previous:||From: Sven R. Kunze||Date: 2017-03-09 20:20:35|
|Subject: Re: adding an immutable variant of to_date|