Re: Patch to be verbose about being unable to read

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: Sean Chittenden <sean(at)chittenden(dot)org>
Cc: pgsql-patches(at)postgresql(dot)org
Subject: Re: Patch to be verbose about being unable to read
Date: 2003-06-20 11:31:23
Message-ID: Pine.LNX.4.44.0306201111510.2297-100000@peter.localdomain
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: 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(at)gmx(dot)net

In response to


Browse pgsql-patches by date

  From Date Subject
Next Message J.R. Nield 2003-06-20 13:17:56 Subtraction carry bug in xlog.c in 7.3 and 7.4
Previous Message Bruno Wolff III 2003-06-20 01:49:56 Re: [HACKERS] psql