Re: Patch to be verbose about being unable to read - Mailing list pgsql-patches

From Peter Eisentraut
Subject Re: Patch to be verbose about being unable to read
Date
Msg-id Pine.LNX.4.44.0306211430320.1882-100000@peter.localdomain
Whole thread Raw
In response to Re: Patch to be verbose about being unable to read ~/.pgpasss...  (Sean Chittenden <sean@chittenden.org>)
List pgsql-patches
Sean Chittenden writes:

> Agreed, though one train of thought is that if someone did put a
> .pgpass file in place that isn't readable, it should be known that
> their efforts are being wasted in vein.

I tried making several dot-files I found in my home directory unreadable
(or unsearchable, in case of a directory): acrorc, antrc, bashrc, cvsrc,
fetchmailrc, inputrc, licq, mozilla, psqlrc, rpmmacros, Xmodmap, xemacs,
xmms.  Bash gave me warning, fetchmail gave me an error (which is
reasonable, because fetchmail doesn't work without configuration), and the
rest just ignored the file.

Open password and private key files might give different results, but as
far as unreadable files go, I say ignore them.

--
Peter Eisentraut   peter_e@gmx.net


pgsql-patches by date:

Previous
From: Tom Lane
Date:
Subject: Re: Patch to be verbose about being unable to read ~/.pgpasss...
Next
From: Dennis Björklund
Date:
Subject: Patch for psql to avoid altering the PGresult strings