From: Tom Lane <tgl@sss.pgh.pa.us>
Date: Wed, 3 Apr 2013 01:15:50 +0000 (-0400)
Subject: Minor robustness improvements for isolationtester.
X-Git-Tag: REL9_1_10~100
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=677fde06afd23f355e3d599eedc3ba7a66ef4e85;p=postgresql

Minor robustness improvements for isolationtester.

Notice and complain about PQcancel() failures.  Also, don't dump core if
an error PGresult doesn't contain severity and message subfields, as it
might not if it was generated by libpq itself.  (We have a longstanding
TODO item to improve that, but in the meantime isolationtester had better
cope.)

I tripped across the latter item while investigating a trouble report on
buildfarm member spoonbill.  As for the former, there's no evidence that
PQcancel failure is actually involved in spoonbill's problem, but it still
seems like a bad idea to ignore an error return code.
---

diff --git a/src/test/isolation/isolationtester.c b/src/test/isolation/isolationtester.c
index 1d76f2cd08..ede12d5771 100644
--- a/src/test/isolation/isolationtester.c
+++ b/src/test/isolation/isolationtester.c
@@ -311,9 +311,22 @@ run_permutation(TestSpec * testspec, int nsteps, Step ** steps)
 				break;
 
 			case PGRES_FATAL_ERROR:
-				/* Detail may contain xid values, so just show primary. */
-				printf("%s:  %s\n", PQresultErrorField(res, PG_DIAG_SEVERITY),
-					   PQresultErrorField(res, PG_DIAG_MESSAGE_PRIMARY));
+				/*
+				 * Detail may contain XID values, so we want to just show
+				 * primary.  Beware however that libpq-generated error results
+				 * may not contain subfields, only an old-style message.
+				 */
+				{
+					const char *sev = PQresultErrorField(res,
+														 PG_DIAG_SEVERITY);
+					const char *msg = PQresultErrorField(res,
+													PG_DIAG_MESSAGE_PRIMARY);
+
+					if (sev && msg)
+						printf("%s:  %s\n", sev, msg);
+					else
+						printf("%s", PQresultErrorMessage(res));
+				}
 				break;
 
 			default: