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 ------ master Details ------- http://git.postgresql.org/pg/commitdiff/83b7584944b3a9df064cccac06822093f1a83793 Modified Files -------------- src/backend/commands/cluster.c | 17 +++++++++++++++++ 1 files changed, 17 insertions(+), 0 deletions(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
