1
0
mirror of https://github.com/postgres/postgres.git synced 2025-07-28 23:42:10 +03:00

Remove postmaster.c's check that NBuffers is at least twice MaxBackends.

With the addition of multiple autovacuum workers, our choices were to delete
the check, document the interaction with autovacuum_max_workers, or complicate
the check to try to hide that interaction.  Since this restriction has never
been adequate to ensure backends can't run out of pinnable buffers, it doesn't
really have enough excuse to live to justify the second or third choices.
Per discussion of a complaint from Andreas Kling (see also bug #3888).

This commit also removes several documentation references to this restriction,
but I'm not sure I got them all.
This commit is contained in:
Tom Lane
2008-03-09 04:56:28 +00:00
parent f4230d2937
commit d9384a4b73
4 changed files with 9 additions and 27 deletions

View File

@ -1,4 +1,4 @@
<!-- $PostgreSQL: pgsql/doc/src/sgml/config.sgml,v 1.167 2008/03/05 16:59:10 momjian Exp $ -->
<!-- $PostgreSQL: pgsql/doc/src/sgml/config.sgml,v 1.168 2008/03/09 04:56:28 tgl Exp $ -->
<chapter Id="runtime-config">
<title>Server Configuration</title>
@ -736,8 +736,7 @@ SET ENABLE_SEQSCAN TO OFF;
memory buffers. The default is typically 32 megabytes
(<literal>32MB</>), but might be less if your kernel settings will
not support it (as determined during <application>initdb</>).
This setting must be at least 128 kilobytes and at least 16
kilobytes times <xref linkend="guc-max-connections">. (Non-default
This setting must be at least 128 kilobytes. (Non-default
values of <symbol>BLCKSZ</symbol> change the minimum.) However,
settings significantly higher than the minimum are usually needed
for good performance. Several tens of megabytes are recommended