Make CLUSTER lock the old table's toast table before copying data.
We must lock out autovacuuming of the old toast table before computing the
OldestXmin horizon we will use. Otherwise, autovacuum could start on the
toast table later, compute a later OldestXmin horizon, and remove as DEAD
toast tuples that we still need (because we think their parent tuples are
only RECENTLY_DEAD). Per further thought about bug #5998.
Branch
------
REL8_4_STABLE
Details
-------
http://git.postgresql.org/pg/commitdiff/aa719c4853ea460d5f9dae5856088205518b51a7
Modified Files
--------------
src/backend/commands/cluster.c | 17 +++++++++++++++++
1 files changed, 17 insertions(+), 0 deletions(-)
