aboutsummaryrefslogtreecommitdiff
path: root/src/backend/utils/adt/xml.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2021-07-05 14:34:47 -0400
committerTom Lane <tgl@sss.pgh.pa.us>2021-07-05 14:34:47 -0400
commit9fa6fe466c9d2eaba4fdd8091203ee61e74d71bf (patch)
tree41b8c5cbbb536fd61009312f6e377440ea379528 /src/backend/utils/adt/xml.c
parent1479c5afdce2c57928dc1322bd71106858a0770f (diff)
downloadpostgresql-9fa6fe466c9d2eaba4fdd8091203ee61e74d71bf.tar.gz
postgresql-9fa6fe466c9d2eaba4fdd8091203ee61e74d71bf.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/utils/adt/xml.c')
0 files changed, 0 insertions, 0 deletions