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 |
Subject: | Re: .pgpass file and unix domain sockets |
Date: | 2006-05-16 16:16:53 |
Message-ID: | 13547.1147796213@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-patches |
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 ...
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2006-05-16 16:27:42 | Re: Compression and on-disk sorting |
Previous Message | Andrew Dunstan | 2006-05-16 16:14:18 | Re: .pgpass file and unix domain sockets |