Rethink blocking annotations in detach-partition-concurrently-[34].
Tom Lane <tgl@sss.pgh.pa.us>
Rethink blocking annotations in detach-partition-concurrently-[34]. In 741d7f104, I tried to make the reports from canceled steps come out after the pg_cancel_backend() steps, since that was the most common ordering before. However, that doesn't ensure that a canceled step doesn't report even later, as shown in a recent failure on buildfarm member idiacanthus. Rather than complicating things even more with additional annotations, let's just force the cancel's effect to be reported first. It's not *that* unnatural-looking. Back-patch to v14 where these test cases appeared. Report: https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=idiacanthus&dt=2021-07-02%2001%3A40%3A04
Files
| Path | Change | +/− |
|---|---|---|
| src/test/isolation/expected/detach-partition-concurrently-3.out | modified | +72 −54 |
| src/test/isolation/expected/detach-partition-concurrently-4.out | modified | +32 −24 |
| src/test/isolation/specs/detach-partition-concurrently-3.spec | modified | +20 −20 |
| src/test/isolation/specs/detach-partition-concurrently-4.spec | modified | +19 −19 |