diff options
author | Tom Lane <tgl@sss.pgh.pa.us> | 2021-07-05 14:34:47 -0400 |
---|---|---|
committer | Tom Lane <tgl@sss.pgh.pa.us> | 2021-07-05 14:34:47 -0400 |
commit | c04c767059b8460b99f6aa4aae5450ab3ee257a3 (patch) | |
tree | 26417b42a867023361f52247571ede8e6600593f /src/backend/access/transam/xlog.c | |
parent | f025f2390e13d7da69da595086fb982bbaf7f329 (diff) | |
download | postgresql-c04c767059b8460b99f6aa4aae5450ab3ee257a3.tar.gz postgresql-c04c767059b8460b99f6aa4aae5450ab3ee257a3.zip |
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
Diffstat (limited to 'src/backend/access/transam/xlog.c')
0 files changed, 0 insertions, 0 deletions