BUG #11455: PQerrorMessage not reset after PQreset

From: postgresql-bklyn(at)sneakemail(dot)com
To: pgsql-bugs(at)postgresql(dot)org
Subject: BUG #11455: PQerrorMessage not reset after PQreset
Date: 2014-09-19 16:57:02
Message-ID: 20140919165702.2558.6058@wrigleys.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

The following bug has been logged on the website:

Bug reference: 11455
Logged by: Caleb Epstein
Email address: postgresql-bklyn(at)sneakemail(dot)com
PostgreSQL version: 9.3.4
Operating system: Linux
Description:

I'm testing application logic to reconnect to my database server after a
connection failure. I'm using PQreset() and I notice that the
PQerrorMessage() result keeps growing after each failed reconnect.

For example, see belwo. My application log messages start with "Database".
The "... Resetting" message is followed by a call to PQreset(). The "FATAL"
messages are the strings returned to be by PQerrorMessage.

Database connection failed. Resetting.
Database reconnect failed: FATAL: terminating connection due to
administrator command
FATAL: terminating connection due to administrator command
FATAL: the database system is shutting down
Database connection unavailable. Cannot persist
Database connection failed. Resetting.
Database reconnect failed: FATAL: terminating connection due to
administrator command
FATAL: terminating connection due to administrator command
FATAL: the database system is shutting down
FATAL: the database system is shutting down

The next error will have 3 instances of "system is shutting down", and so
on.

Thanks!

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2014-09-19 19:57:21 Re: BUG #11455: PQerrorMessage not reset after PQreset
Previous Message David G Johnston 2014-09-19 14:05:31 Re: BUG #11441: Weird (and seems wrong) behavior of partial indexes with order by/limit