Fix parallel operations that prevent oldest xmin from advancing.
authorAmit Kapila <akapila@postgresql.org>
Fri, 19 Nov 2021 03:34:40 +0000 (09:04 +0530)
committerAmit Kapila <akapila@postgresql.org>
Fri, 19 Nov 2021 03:34:40 +0000 (09:04 +0530)
commit0f0cfb494004befb0f6e89d3129347869420c509
tree575c00db6d52c852f556cda8415f7b6b157636fe
parent0cd6d3b3c5aeac81903aa7de92e406f8567898a2
Fix parallel operations that prevent oldest xmin from advancing.

While determining xid horizons, we skip over backends that are running
Vacuum. We also ignore Create Index Concurrently, or Reindex Concurrently
for the purposes of computing Xmin for Vacuum. But we were not setting the
flags corresponding to these operations when they are performed in
parallel which was preventing Xid horizon from advancing.

The optimization related to skipping Create Index Concurrently, or Reindex
Concurrently operations was implemented in PG-14 but the fix is the same
for the Parallel Vacuum as well so back-patched till PG-13.

Author: Masahiko Sawada
Reviewed-by: Amit Kapila
Backpatch-through: 13
Discussion: https://postgr.es/m/CAD21AoCLQqgM1sXh9BrDFq0uzd3RBFKi=Vfo6cjjKODm0Onr5w@mail.gmail.com
src/backend/access/heap/vacuumlazy.c
src/backend/access/nbtree/nbtsort.c
src/backend/storage/ipc/procarray.c
src/include/storage/proc.h