Re: Patch to be verbose about being unable to read ~/.pgpasss...

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Sean Chittenden <sean(at)chittenden(dot)org>
Cc: Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-patches(at)postgresql(dot)org
Subject: Re: Patch to be verbose about being unable to read ~/.pgpasss...
Date: 2003-06-20 20:09:58
Message-ID: 20291.1056139798@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-patches

Sean Chittenden <sean(at)chittenden(dot)org> writes:
> Would you like me to add an interface that'd allow stderr to be
> redirected in the case of defaultNoticeProcessor()?

No, the application is supposed to set a notice processor if it doesn't
want stuff going to stderr. I don't think that stuff needs to be
redesigned.

> We can stat a file that is owned by root and not readable to the user.
> In such a case, because the user isn't able to read the file, all
> libpq applications will fail making it effectively possible for the
> system admin to shut off all applications that use libpq.

Hardly, since the user can simply remove or rename the file. It's in
his home directory, remember? (If he can't write his home directory
then whether libpq works is the least of his troubles.)

regards, tom lane

In response to

Responses

Browse pgsql-patches by date

  From Date Subject
Next Message Sailesh Krishnamurthy 2003-06-20 21:23:08 Re: [HACKERS] psql
Previous Message Sean Chittenden 2003-06-20 18:48:20 Re: Patch to be verbose about being unable to read ~/.pgpasss...