From: | Dmitriy Igrishin <dmitigr(at)gmail(dot)com> |
---|---|
To: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Multiple error reports. |
Date: | 2013-06-06 17:12:43 |
Message-ID: | CAAfz9KNbibCF9yD7Gv+XFUtB6eVAL_dDGe9AgrSqDmYyu5fRkg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
According to http://www.postgresql.org/docs/9.2/static/libpq-async.html
"Even when PQresultStatus indicates a fatal error, PQgetResult should be
called
until it returns a null pointer, to allow libpq to process the error
information completely."
In libpq/fe-exec.c:PQexecFinish() error messages merges if more than one
error
retrieved from the backend.
Can you please explain, in what cases the backend returns multiple error
reports,
and is it guaranteed that all of them with the same SQLSTATE code? If it
is, I would
also like to know, what a reason for sending the same error in multiple
error
reports?
--
// Dmitriy.
From | Date | Subject | |
---|---|---|---|
Next Message | Josh Berkus | 2013-06-06 17:24:13 | Re: Redesigning checkpoint_segments |
Previous Message | Josh Berkus | 2013-06-06 17:00:15 | Re: Redesigning checkpoint_segments |