Skip to content

Commit ac148a2

Browse files
Mark vacuum_defer_cleanup_age as PGC_POSTMASTER.
Following bug analysis of #7819 by Tom Lane
1 parent 3c6e719 commit ac148a2

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
@@ -2059,8 +2059,7 @@ SET ENABLE_SEQSCAN TO OFF;
20592059
is measured in terms of number of write transactions occurring on the
20602060
primary server, it is difficult to predict just how much additional
20612061
grace time will be made available to standby queries.
2062-
This parameter can only be set in the <filename>postgresql.conf</>
2063-
file or on the server command line.
2062+
This parameter can only be set at server start.
20642063
</para>
20652064
<para>
20662065
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
@@ -1853,7 +1853,12 @@ static struct config_int ConfigureNamesInt[] =
18531853
},
18541854

18551855
{
1856-
{"vacuum_defer_cleanup_age", PGC_SIGHUP, REPLICATION_MASTER,
1856+
/*
1857+
* Setting this to a higher value without restarting postmaster
1858+
* can cause various bugs in TOAST object removal, CLUSTER and
1859+
* possibly other places, so this must be changed only on restart.
1860+
*/
1861+
{"vacuum_defer_cleanup_age", PGC_POSTMASTER, REPLICATION_MASTER,
18571862
gettext_noop("Number of transactions by which VACUUM and HOT cleanup should be deferred, if any."),
18581863
NULL
18591864
},

0 commit comments

Comments
 (0)