pgsql: Remove postmaster.c's check that NBuffers is at least twice - Mailing list pgsql-committers

From tgl@postgresql.org (Tom Lane)
Subject pgsql: Remove postmaster.c's check that NBuffers is at least twice
Date
Msg-id 20080309045628.BDB10753F33@cvs.postgresql.org
Whole thread Raw
List pgsql-committers
Log Message:
-----------
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.

Modified Files:
--------------
    pgsql/doc/src/sgml:
        config.sgml (r1.167 -> r1.168)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/config.sgml?r1=1.167&r2=1.168)
    pgsql/src/backend/postmaster:
        postmaster.c (r1.552 -> r1.553)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/postmaster/postmaster.c?r1=1.552&r2=1.553)
    pgsql/src/backend/utils/misc:
        guc.c (r1.433 -> r1.434)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/misc/guc.c?r1=1.433&r2=1.434)
        postgresql.conf.sample (r1.236 -> r1.237)

(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/misc/postgresql.conf.sample?r1=1.236&r2=1.237)

pgsql-committers by date:

Previous
From: tgl@postgresql.org (Tom Lane)
Date:
Subject: pgsql: Change patternsel() so that instead of switching from a pure
Next
From: teodor@postgresql.org (Teodor Sigaev)
Date:
Subject: pgsql: Revert changes of CompareTSQ: it affects existing btree indexes.