pgsql: Be more robust when strerror() doesn't give a useful result.

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Be more robust when strerror() doesn't give a useful result.
Date: 2013-11-07 21:34:06
Message-ID: E1VeXDK-000199-IE@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Be more robust when strerror() doesn't give a useful result.

Back-patch commits 8e68816cc2567642c6fcca4eaac66c25e0ae5ced and
8dace66e0735ca39b779922d02c24ea2686e6521 into the stable branches.
Buildfarm testing revealed no great portability surprises, and it
seems useful to have this robustness improvement in all branches.

Branch
------
REL8_4_STABLE

Details
-------
http://git.postgresql.org/pg/commitdiff/3eb777671b942001e3f8c740a607348f62df038d

Modified Files
--------------
src/backend/utils/error/elog.c | 187 +++++++++++++++++++++++++++++++++++++++-
1 file changed, 183 insertions(+), 4 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Kevin Grittner 2013-11-07 22:39:05 pgsql: Silence benign warnings from clang version 3.0-6ubuntu3.
Previous Message Tom Lane 2013-11-07 19:42:00 pgsql: Prevent display of dropped columns in row constraint violation m