Forest Wilkinson <lyris-pg(at)tibit(dot)com> writes:
> 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.
> Why isn't PGRES_NONFATAL_ERROR returned for queries in an aborted
> transaction state?
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. AFAICS the *only* case where you get
PGRES_NONFATAL_ERROR is when you pass a null PGresult pointer to
PQresultStatus(), which in the current code is a pretty dubious choice
(PGRES_EMPTY_QUERY is arguably better).
regards, tom lane
In response to
pgsql-interfaces by date
|Next:||From: Forest Wilkinson||Date: 2003-05-23 00:23:45|
|Subject: Re: PGRES_FATAL_ERROR from queries in transaction abort state? |
|Previous:||From: Forest Wilkinson||Date: 2003-05-22 20:58:10|
|Subject: PGRES_FATAL_ERROR from queries in transaction abort state?|