From: Forest Wilkinson <lyris-pg@tibit.com>
To: pgsql-interfaces@postgresql.org
Subject: Re: PGRES_FATAL_ERROR from queries in transaction abort state?
Date: Thu, 22 May 2003 17:23:45 -0700
Message-ID: <otpqcvgqsa205b6gfut5mdivm08e5ttr78@4ax.com> (raw)
In-Reply-To: <12311.1053648387@sss.pgh.pa.us>
References: <mldqcvkst5usunkue57995ls4cvr46q60b@4ax.com>
<12311.1053648387@sss.pgh.pa.us>
>> I am maintaining code that uses libpq, and takes PGRES_FATAL_ERROR to
>> mean the database connection can no longer be used.
>
>It has never meant that. Only connection status going to CONNECTION_BAD
>would mean that.
Okay. What does it mean?
>I think that the original design intended the code PGRES_NONFATAL_ERROR
>to be used for what we now call a WARNING; but in point of fact it's not
>being used at all, because warnings aren't reported through
>PQresultStatus.
In that case, wouldn't PGRES_NONFATAL_ERROR be a more appropriate
choice for queries that fail due to an aborted transaction? I can't
think of how this condition could be considered fatal.
>AFAICS the *only* case where you get
>PGRES_NONFATAL_ERROR is when you pass a null PGresult pointer to
>PQresultStatus(),
I got one today by passing ";" to PQexec().
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-interfaces@postgresql.org
Cc: lyris-pg@tibit.com
Subject: Re: PGRES_FATAL_ERROR from queries in transaction abort state?
In-Reply-To: <otpqcvgqsa205b6gfut5mdivm08e5ttr78@4ax.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox