mirror of
https://github.com/postgres/postgres.git
synced 2026-03-12 13:44:02 -04:00
7a1e7b291d
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. |
||
|---|---|---|
| .. | ||
| examples | ||
| isolation | ||
| locale | ||
| mb | ||
| modules | ||
| perl | ||
| regress | ||
| ssl | ||
| thread | ||
| Makefile | ||