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

hackers - any opinions?

The biggest downside would be that a pgpass file would be version
specific for this feature. 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: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
CC: Joachim Wieland <joe(at)mcknight(dot)de>, pgsql-patches(at)postgresql(dot)org
References: <20060516122554(dot)GA4009(at)mcknight(dot)de>
<11676(dot)1147787022(at)sss(dot)pgh(dot)pa(dot)us> <4469F499(dot)1040002(at)dunslane(dot)net>
<13302(dot)1147795016(at)sss(dot)pgh(dot)pa(dot)us> <4469FA5A(dot)3090504(at)dunslane(dot)net>

Andrew Dunstan <andrew(at)dunslane(dot)net> 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 for an explicit entry
> covering all Unix Domain sockets - it took me by some surprise to find a
> while back that "localhost" covers that case - it seems a mismatch with
> how pg_hba.conf works.

Well, that'd break existing .pgpass files (unless we match localhost
too, which seems to defeat the purpose). But maybe it's worth doing
for consistency's sake. I think we should bring it up on a more
widely read list than -patches if you want to propose a
non-backwards-compatible change ...