Skip to content

Commit 9dd9993

Browse files
Mark vacuum_defer_cleanup_age as PGC_POSTMASTER.
Following bug analysis of #7819 by Tom Lane
1 parent 231dbb3 commit 9dd9993

File tree

2 files changed

+7
-3
lines changed

2 files changed

+7
-3
lines changed

doc/src/sgml/config.sgml

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2288,8 +2288,7 @@ SET ENABLE_SEQSCAN TO OFF;
22882288
is measured in terms of number of write transactions occurring on the
22892289
primary server, it is difficult to predict just how much additional
22902290
grace time will be made available to standby queries.
2291-
This parameter can only be set in the <filename>postgresql.conf</>
2292-
file or on the server command line.
2291+
This parameter can only be set at server start.
22932292
</para>
22942293
<para>
22952294
You should also consider setting <varname>hot_standby_feedback</>

src/backend/utils/misc/guc.c

Lines changed: 6 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1880,7 +1880,12 @@ static struct config_int ConfigureNamesInt[] =
18801880
},
18811881

18821882
{
1883-
{"vacuum_defer_cleanup_age", PGC_SIGHUP, REPLICATION_MASTER,
1883+
/*
1884+
* Setting this to a higher value without restarting postmaster
1885+
* can cause various bugs in TOAST object removal, CLUSTER and
1886+
* possibly other places, so this must be changed only on restart.
1887+
*/
1888+
{"vacuum_defer_cleanup_age", PGC_POSTMASTER, REPLICATION_MASTER,
18841889
gettext_noop("Number of transactions by which VACUUM and HOT cleanup should be deferred, if any."),
18851890
NULL
18861891
},

0 commit comments

Comments
 (0)