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

pgsql: Utilize the visibility map in autovacuum, too.

From: heikki(at)postgresql(dot)org (Heikki Linnakangas)
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Utilize the visibility map in autovacuum, too.
Date: 2008-12-04 11:42:24
Message-ID: 20081204114224.7E08A7545A4@cvs.postgresql.org (view raw or flat)
Thread:
Lists: pgsql-committers
Log Message:
-----------
Utilize the visibility map in autovacuum, too. There was an oversight in
the visibility map patch that because autovacuum always sets
VacuumStmt->freeze_min_age, visibility map was never used for autovacuum,
only for manually launched vacuums. This patch introduces a new scan_all
field to VacuumStmt, indicating explicitly whether the visibility map
should be used, or the whole relation should be scanned, to advance
relfrozenxid. Anti-wraparound vacuums still need to scan all pages.

Modified Files:
--------------
    pgsql/src/backend/commands:
        vacuumlazy.c (r1.112 -> r1.113)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/commands/vacuumlazy.c?r1=1.112&r2=1.113)
    pgsql/src/backend/nodes:
        copyfuncs.c (r1.413 -> r1.414)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/nodes/copyfuncs.c?r1=1.413&r2=1.414)
        equalfuncs.c (r1.338 -> r1.339)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/nodes/equalfuncs.c?r1=1.338&r2=1.339)
    pgsql/src/backend/parser:
        gram.y (r2.641 -> r2.642)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/parser/gram.y?r1=2.641&r2=2.642)
    pgsql/src/backend/postmaster:
        autovacuum.c (r1.87 -> r1.88)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/postmaster/autovacuum.c?r1=1.87&r2=1.88)
    pgsql/src/include/nodes:
        parsenodes.h (r1.379 -> r1.380)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/include/nodes/parsenodes.h?r1=1.379&r2=1.380)

pgsql-committers by date

Next:From: Magnus HaganderDate: 2008-12-04 14:07:42
Subject: pgsql: Comment said we don't free the lockarray, and why.
Previous:From: Teodor SigaevDate: 2008-12-04 11:10:06
Subject: pgsql: Initialize GISTScanOpaque->qual_ok even if there is no

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