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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: Sean Chittenden <sean(at)chittenden(dot)org>, pgsql-patches(at)postgresql(dot)org
Subject: Re: Patch to be verbose about being unable to read ~/.pgpasss...
Date: 2003-06-24 03:55:06
Message-ID: 16599.1056426906@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-patches

Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> I don't have problems sending the output to stderr myself.

That's because you don't run libpq in any contexts where that behavior
is inappropriate ... but there are plenty such contexts. Most GUI
applications will want to trap any and all notices and put them up in
a window; sending to stderr is likely to mean sending to /dev/null,
or at best a logfile that the user will never look at.

regards, tom lane

In response to

Browse pgsql-patches by date

  From Date Subject
Next Message Reuven M. Lerner 2003-06-24 05:18:44 Many Pl/PgSQL parameters -> AllocSetAlloc(128)?
Previous Message Tom Lane 2003-06-24 03:51:49 Re: [HACKERS] Subtraction carry bug in xlog.c in 7.3 and 7.4