Re: v8.1: Error severity on libpq PGconn* - Mailing list pgsql-interfaces

From Bruce Momjian
Subject Re: v8.1: Error severity on libpq PGconn*
Date
Msg-id 200803071754.m27Hs5k21135@momjian.us
Whole thread Raw
In response to Re: v8.1: Error severity on libpq PGconn*  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-interfaces
Added to TODO:
       o Add SQLSTATE severity to PGconn return status
         http://archives.postgresql.org/pgsql-interfaces/2007-11/msg00015.php

---------------------------------------------------------------------------

Tom Lane wrote:
> Jeffrey Brendecke <yakhki@yahoo.de> writes:
> > Is there a recommended way to get the error severity (ERROR vs. FATAL vs. PANIC, etc.) off a PGconn* as there is
fora PGresult* using PQresultErrorField()?
 
> > For example, when I pass in a non-existent database name when creating a connection, I get the following message:
> 
> > FATAL:  database "xxxxxx" does not exist
> 
> What you're really wishing here is that errors generated within libpq
> itself had SQLSTATE and other decoration.  They don't :-(.  Improving
> this is on the to-do list, but someone is going to have to sit down and
> do several days/weeks of hard and mostly-boring work to make it happen.
> Do you want to volunteer?
> 
>             regards, tom lane
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 1: if posting/reading through Usenet, please send an appropriate
>        subscribe-nomail command to majordomo@postgresql.org so that your
>        message can get through to the mailing list cleanly

--  Bruce Momjian  <bruce@momjian.us>        http://momjian.us EnterpriseDB
http://postgres.enterprisedb.com
 + If your life is a hard drive, Christ can be your backup. +


pgsql-interfaces by date:

Previous
From: "jing han"
Date:
Subject: jing h sent you a special gift
Next
From: "Edmund Bacon"
Date:
Subject: ECPG connection timeouts