Magnus Hagander <mag...@hagander.net> writes: > Hmm. Good point. I didn't realize they already had to be ready to get a > non-default path back.
Yeah, if it weren't for that, this would definitely be a hazardous change. But AFAICS, an app that has a problem with this proposal was broken already, it just didn't know it. > Of course, the documentation just says it'll return a hostname. It should > probably mention that it can return the unix socket path as well - but > that's something that's missing already. Agreed, will fix that. regards, tom lane -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers