Skip site navigation (1) Skip section navigation (2)

Peripheral Links

Header And Logo

PostgreSQL
| The world's most advanced open source database.

Site Navigation

Search archives
  Advanced Search

Re: v8.1: Error severity on libpq PGconn*


  • From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
  • To: Jeffrey Brendecke <yakhki(at)yahoo(dot)de>
  • Cc: pgsql-interfaces(at)postgresql(dot)org
  • Subject: Re: v8.1: Error severity on libpq PGconn*
  • Date: Mon, 26 Nov 2007 21:24:33 -0500
  • Message-id: <8904.1196130273@sss.pgh.pa.us> <text/plain>

Jeffrey Brendecke <yakhki(at)yahoo(dot)de> writes:
> Is there a recommended way to get the error severity (ERROR vs. FATAL vs. PANIC, etc.) off a PGconn* as there is for a 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



Home | Main Index | Thread Index

Privacy Policy | About PostgreSQL
Copyright © 1996 – 2012 PostgreSQL Global Development Group