| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andreas Pflug <pgadmin(at)pse-consulting(dot)de> |
| Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, Dave Page <dpage(at)vale-housing(dot)co(dot)uk>, Robert Treat <xzilla(at)users(dot)sourceforge(dot)net>, Magnus Hagander <mha(at)sollentuna(dot)net>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: [PATCHES] default database creation with initdb |
| Date: | 2005-06-20 14:48:07 |
| Message-ID: | 6974.1119278887@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Andreas Pflug <pgadmin(at)pse-consulting(dot)de> writes:
> Tom Lane wrote:
>> If it's a server-side failure it should have a SQLSTATE code.
> Specifically, I'm talking about
> "no pg_hba.conf entry for ....",
ERRCODE_INVALID_AUTHORIZATION_SPECIFICATION
> "Ident authentication failed.." (both server sice)
Ditto. Do you need to know the difference? What exactly would client
code do differently for these two cases?
> and "Is the server running on host ..." from libpq
libpq doesn't currently assign SQLSTATEs to internally detected errors
... someday someone should fix that.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dave Page | 2005-06-20 15:34:40 | Re: [PATCHES] default database creation with initdb |
| Previous Message | Tom Lane | 2005-06-20 14:43:12 | Re: quote_boolean() and friends missing |