From efa4a9462a072b4cd6459058df274dd23022d0e2 Mon Sep 17 00:00:00 2001 From: Peter Geoghegan Date: Fri, 11 Feb 2022 18:26:15 -0800 Subject: Consolidate VACUUM xid cutoff logic. Push the logic for determining whether or not a VACUUM operation will be aggressive down into vacuum_set_xid_limits(). This makes the function's signature significantly simpler, and seems clearer overall. Author: Peter Geoghegan Discussion: https://postgr.es/m/CAH2-WzkymFbz6D_vL+jmqSn_5q1wsFvFrE+37yLgL_Rkfd6Gzg@mail.gmail.com --- src/backend/commands/cluster.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) (limited to 'src/backend/commands/cluster.c') diff --git a/src/backend/commands/cluster.c b/src/backend/commands/cluster.c index 2e8efe4f8fc..02a7e94bf9b 100644 --- a/src/backend/commands/cluster.c +++ b/src/backend/commands/cluster.c @@ -857,8 +857,7 @@ copy_table_data(Oid OIDNewHeap, Oid OIDOldHeap, Oid OIDOldIndex, bool verbose, * not to be aggressive about this. */ vacuum_set_xid_limits(OldHeap, 0, 0, 0, 0, - &OldestXmin, &FreezeXid, NULL, &MultiXactCutoff, - NULL); + &OldestXmin, &FreezeXid, &MultiXactCutoff); /* * FreezeXid will become the table's new relfrozenxid, and that mustn't go -- cgit v1.2.3