Skip to content

Commit e2501d8

Browse files
committed
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.
1 parent c776cd4 commit e2501d8

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

src/test/isolation/isolationtester.c

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -609,7 +609,7 @@ run_permutation(TestSpec * testspec, int nsteps, Step ** steps)
609609
if (!PQsendQuery(conn, step->sql))
610610
{
611611
fprintf(stdout, "failed to send query for step %s: %s\n",
612-
step->name, PQerrorMessage(conns[1 + step->session]));
612+
step->name, PQerrorMessage(conn));
613613
exit_nicely();
614614
}
615615

@@ -739,7 +739,7 @@ try_complete_step(Step * step, int flags)
739739
if (PQresultStatus(res) != PGRES_TUPLES_OK)
740740
{
741741
fprintf(stderr, "lock wait query failed: %s",
742-
PQerrorMessage(conn));
742+
PQerrorMessage(conns[0]));
743743
exit_nicely();
744744
}
745745
ntuples = PQntuples(res);

0 commit comments

Comments
 (0)