postgres.git / summary / log / commit / refs
commit dab476d75b8af56e919d2d3b05d123e2c0b7ea4a
Author: Fujii Masao <fujii@postgresql.org>
Date: Tue Nov 03 05:54:02 2026 +0000
First released in: 18.7, 19.0
doc: Correct setting restrictions for vacuum_max_eager_freeze_failure_rate
The documentation incorrectly stated that this parameter could only
be set in postgresql.conf or on the server command line. However, it
is a PGC_USERSET parameter and can therefore be changed by any user
within a session.
Remove the incorrect restriction while retaining the note about the
per-table storage parameter override.
Backpatch to v18, where this parameter was introduced.
Author: Afrah Razzak <mypg.afrah@gmail.com>
Reviewed-by: Fujii Masao <masao.fujii@gmail.com>
Discussion: https://postgr.es/m/CAAJ6gzGeup6WPpraF1g6iWYOQsvLmhKk94acJ=-iq+Gg_x9W0w@mail.gmail.com
Backpatch-through: 18
doc/src/sgml/config.sgml | 5 +----
1 file changed, 1 insertion(+), 4 deletions(-)
diff --git a/doc/src/sgml/config.sgml b/doc/src/sgml/config.sgml
index 61fda40d771..289058484ab 100644
--- a/doc/src/sgml/config.sgml
+++ b/doc/src/sgml/config.sgml
@@ -10263,10 +10263,7 @@ COPY postgres_log FROM '/full/path/to/logfile.csv' WITH csv;
</para>
<para>
- This parameter can only be set in the
- <filename>postgresql.conf</filename> file or on the server command
- line; but the setting can be overridden for individual tables by
- changing the
+ The setting can be overridden for individual tables by changing the
<link linkend="reloption-vacuum-max-eager-freeze-failure-rate">
corresponding table storage parameter</link>.
For more information on tuning vacuum's freezing behavior,
[parent: 316861101e8c]