[HACKERS] chomp PQerrorMessage() in backend uses - Mailing list pgsql-hackers

From Peter Eisentraut
Subject [HACKERS] chomp PQerrorMessage() in backend uses
Date
Msg-id aaa2ad35-93f9-bd65-6361-c53365120e9a@2ndquadrant.com
Whole thread Raw
Responses Re: [HACKERS] chomp PQerrorMessage() in backend uses  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Here is a patch to systematically trim the trailing newlines off
PQerrorMessage() results in backend uses (dblink, postgres_fdw,
libpqwalreceiver).

I noticed that there are some inconsistent assumptions about whether
PQerrorMessage() can ever return NULL.  From the code, I think that
should not be possible, but some code appears to be prepared for it.
Other code is not.  What is correct?

-- 
Peter Eisentraut              http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

Attachment

pgsql-hackers by date:

Previous
From: Ashutosh Sharma
Date:
Subject: Re: [HACKERS] pageinspect: Hash index support
Next
From: Christoph Berg
Date:
Subject: Re: [HACKERS] One-shot expanded output in psql using \gx