Re: [HACKERS] Connection to PostgreSQL Using Certificate: Wrong Permissions on Private Key File

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "korry" <korry(dot)douglas(at)enterprisedb(dot)com>
Cc: "Kevin Hunter" <hunteke(at)earlham(dot)edu>, "Angus Black Atkins-Trimnell" <trimnell(at)uic(dot)edu>, "Postgres General List" <pgsql-general(at)postgresql(dot)org>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: [HACKERS] Connection to PostgreSQL Using Certificate: Wrong Permissions on Private Key File
Date: 2008-04-01 05:13:11
Message-ID: 20670.1207026791@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

"korry" <korry(dot)douglas(at)enterprisedb(dot)com> writes:
> Hmmm... I'm not crazy about libpq printing error messages to stderr.

Me neither, feel free to submit a patch.

The basic problem here is that the obvious fix involves feeding
the message to a PQnoticeProcessor callback, but these messages
occur during connection setup and there's no way to have called
PQsetNoticeProcessor yet.

So I think you've got to invent some green-field API if you want
to improve it, and that means nothing will happen out in the
real world for three to five years :-(

regards, tom lane

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Tomasz Ostrowski 2008-04-01 06:18:36 Re: simple update queries take a long time - postgres 8.3.1
Previous Message Stephen Frost 2008-04-01 03:38:11 Re: Survey: renaming/removing script binaries (createdb, createuser...)

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2008-04-01 05:35:24 Re: Re: [HACKERS] How embarrassing: optimization of a one-shot query doesn't work
Previous Message Andrew Dunstan 2008-04-01 02:12:06 Re: How embarrassing: optimization of a one-shot query doesn't work