Fix minor bug in isolationtester.
If the lock wait query failed, isolationtester would report the
PQerrorMessage from some other connection, meaning there would be
no message or an unrelated one. This seems like a pretty unlikely
occurrence, but if it did happen, this bug could make it really
difficult/confusing to figure out what happened. That seems to
justify patching all the way back.
In passing, clean up another place where the "wrong" conn was used
for an error report. That one's not actually buggy because it's
a different alias for the same connection, but it's still confusing
to the reader.
Branch
------
REL_11_STABLE
Details
-------
https://git.postgresql.org/pg/commitdiff/0a21c6d9e512ad981273b74b61187ec6063de243
Modified Files
--------------
src/test/isolation/isolationtester.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)