| From: | Sean Chittenden <chitt(at)speakeasy(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | PostgreSQL-patches <pgsql-patches(at)postgresql(dot)org> |
| Subject: | Re: Slightly better testing for pg_ctl(1)'s -w... |
| Date: | 2004-10-11 19:02:09 |
| Message-ID: | 0CFE14AB-1BB8-11D9-BCB2-000A95C705DC@speakeasy.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-patches |
>>> ... it should have a SQLSTATE assigned, so you could
>>> check for ERRCODE_INVALID_AUTHORIZATION_SPECIFICATION ...
>
>> Ok, I've read over the code a little bit... it doesn't seem like
>> there's an obvious way to get the error code via libpq(3).
>
> Hmmm ... I was thinking of PQresultErrorField, but you don't actually
> get a PGresult from a connection failure, so that's no good :-(.
>
> I suppose we need to think about extending libpq so that a SQLSTATE
> can be retrieved for connection-level failures. That kinda moves
> it out of the realm of bug-fix-for-beta though.
Whew, glad it wasn't me. Could we (ie Bruce) add getting the raw
errcode as an 8.1 TODO item? In the mean time, are you going to commit
the pg_ctl patch? -sc
--
Sean Chittenden
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2004-10-11 19:10:47 | Re: plperl features |
| Previous Message | Peter Eisentraut | 2004-10-11 18:59:01 | Re: plperl features |