Re: [HACKERS] .pgpass file and unix domain sockets

2006-05-11 Thread Martijn van Oosterhout
On Wed, May 10, 2006 at 09:34:38PM -0400, Tom Lane wrote: > I'm not sure if that's a bug or not. Arguably, different socket paths > might point to different servers for which you need different passwords. > If we did want unix-socket connections to search for "localhost" > regardless of socket pat

Re: [HACKERS] .pgpass file and unix domain sockets

2006-05-10 Thread Tom Lane
Joachim Wieland <[EMAIL PROTECTED]> writes: > The documentation suggests that the hostname part of .pgpass can be set to > "localhost" to allow for automatic unix domain socket authentication. This > doesn't seem to work. Instead you have to set the directory of the socket as > the hostname part.

[HACKERS] .pgpass file and unix domain sockets

2006-05-10 Thread Joachim Wieland
The documentation for the .pgpass file seems to be incorrect with respect to unix domain sockets. There's also a user comment saying that: http://www.postgresql.org/docs/8.1/interactive/libpq-pgpass.html The documentation suggests that the hostname part of .pgpass can be set to "localhost" to al