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.0306201111510.2297-100000@peter.localdomain
Whole thread Raw
In response to Patch to be verbose about being unable to read ~/.pgpasss...  (Sean Chittenden <sean@chittenden.org>)
Responses Re: Patch to be verbose about being unable to read
Re: Patch to be verbose about being unable to read ~/.pgpasss...
List pgsql-patches
Sean Chittenden writes:

> Howdy.  Quick chump patch: if libpq finds a ~/.pgpass but can't stat
> it, print something to stderr letting the user know.  If someone went
> out of their way to put a .pgpass file in place, if they can't read
> it, it seems worth while to alert them to the fact that it's not being
> used (ex: root creates a .pgpass file but forgets to chown it).

You cannot assume that stderr is meaningful in all applications using
libpq.  (Consider PHP.)  I think you need to report this using the normal
error reporting mechanism.

--
Peter Eisentraut   peter_e@gmx.net


pgsql-patches by date:

Previous
From: Sean Chittenden
Date:
Subject: Re: Patch to be verbose about being unable to read ~/.pgpasss...
Next
From: "J.R. Nield"
Date:
Subject: Subtraction carry bug in xlog.c in 7.3 and 7.4