Skip site navigation (1) Skip section navigation (2)

pgsql: To reduce confusion over whether VACUUM FULL is needed for

From: tgl(at)postgresql(dot)org (Tom Lane)
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: To reduce confusion over whether VACUUM FULL is needed for
Date: 2008-12-11 18:16:18
Message-ID: 20081211181618.AE7857545A4@cvs.postgresql.org (view raw or flat)
Thread:
Lists: pgsql-committers
Log Message:
-----------
To reduce confusion over whether VACUUM FULL is needed for anti-wraparound
vacuuming (it's not), say "database-wide VACUUM" instead of "full-database
VACUUM" in the relevant hint messages.  Also, document the permissions needed
to do this.  Per today's discussion.

Modified Files:
--------------
    pgsql/doc/src/sgml:
        maintenance.sgml (r1.87 -> r1.88)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/maintenance.sgml?r1=1.87&r2=1.88)
    pgsql/doc/src/sgml/ref:
        vacuum.sgml (r1.53 -> r1.54)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/ref/vacuum.sgml?r1=1.53&r2=1.54)
    pgsql/src/backend/access/transam:
        varsup.c (r1.81 -> r1.82)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/transam/varsup.c?r1=1.81&r2=1.82)

pgsql-committers by date

Next:From: Tom LaneDate: 2008-12-12 00:41:46
Subject: Re: pgsql: Append major version number and for libraries soname major
Previous:From: Peter EisentrautDate: 2008-12-11 10:25:17
Subject: pgsql: The macros NULL_DEV and DEVNULL were both used to work around

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group