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

2006-05-17 Thread Bruce Momjian
Original Message Subject: Re: [PATCHES] .pgpass file and unix domain sockets Date: Tue, 16 May 2006 12:16:53 -0400 From: Tom Lane [EMAIL PROTECTED] To: Andrew Dunstan [EMAIL PROTECTED] CC: Joachim Wieland [EMAIL PROTECTED], pgsql

[PATCHES] .pgpass file and unix domain sockets

2006-05-16 Thread Joachim Wieland
Since no decision has been reached in http://archives.postgresql.org/pgsql-hackers/2006-05/msg00295.php I send in the appended documentation patch to fix at least the documentation. Personally I think that there is no need to invent a new syntax since we can express everything already with the

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

2006-05-16 Thread Tom Lane
Joachim Wieland [EMAIL PROTECTED] writes: I send in the appended documentation patch to fix at least the documentation. This is wrong according to my tests. localhost *does* work, at least in some cases. regards, tom lane ---(end of

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

2006-05-16 Thread Andrew Dunstan
Tom Lane wrote: Joachim Wieland [EMAIL PROTECTED] writes: I send in the appended documentation patch to fix at least the documentation. This is wrong according to my tests. localhost *does* work, at least in some cases. As I understand it, the only case where it doesn't is

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

2006-05-16 Thread Tom Lane
Andrew Dunstan [EMAIL PROTECTED] writes: Tom Lane wrote: This is wrong according to my tests. localhost *does* work, at least in some cases. As I understand it, the only case where it doesn't is where an explicit host connection parameter pointing to the socket directory, or the same via

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

2006-05-16 Thread Andrew Dunstan
Tom Lane wrote: Andrew Dunstan [EMAIL PROTECTED] writes: Tom Lane wrote: This is wrong according to my tests. localhost *does* work, at least in some cases. As I understand it, the only case where it doesn't is where an explicit host connection parameter pointing to the

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

2006-05-16 Thread Tom Lane
Andrew Dunstan [EMAIL PROTECTED] writes: Tom Lane wrote: Personally I wouldn't object to making it match localhost in all cases. That's what the documentation says, and the use-case for doing something more complicated seems pretty thin. I almost agree. If anything, I'd prefer to provide

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

2006-05-16 Thread Joachim Wieland
On Tue, May 16, 2006 at 09:43:42AM -0400, Tom Lane wrote: Joachim Wieland [EMAIL PROTECTED] writes: I send in the appended documentation patch to fix at least the documentation. This is wrong according to my tests. localhost *does* work, at least in some cases. I see the problem now... I

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

2006-05-16 Thread Bruce Momjian
. The badness of this is somewhat mitigated by the ability we now have to specify an alternative pgpassfile location. cheers andrew Original Message Subject:Re: [PATCHES] .pgpass file and unix domain sockets Date: Tue, 16 May 2006 12:16:53 -0400 From