pgsql: Fix logic in lazy vacuum to decide if it's worth trying to - Mailing list pgsql-committers

From heikki@postgresql.org (Heikki Linnakangas)
Subject pgsql: Fix logic in lazy vacuum to decide if it's worth trying to
Date
Msg-id 20090106145614.0C65A754A1C@cvs.postgresql.org
Whole thread Raw
List pgsql-committers
Log Message:
-----------
Fix logic in lazy vacuum to decide if it's worth trying to truncate the heap.
If the table was smaller than REL_TRUNCATE_FRACTION (= 16) pages, we always
tried to acquire AccessExclusiveLock on it even if there was no empty pages
at the end.

Report by Simon Riggs. Back-patch all the way to 7.4.

Tags:
----
REL7_4_STABLE

Modified Files:
--------------
    pgsql/src/backend/commands:
        vacuumlazy.c (r1.32.2.2 -> r1.32.2.3)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/commands/vacuumlazy.c?r1=1.32.2.2&r2=1.32.2.3)

pgsql-committers by date:

Previous
From: heikki@postgresql.org (Heikki Linnakangas)
Date:
Subject: pgsql: Fix logic in lazy vacuum to decide if it's worth trying to
Next
From: tgl@postgresql.org (Tom Lane)
Date:
Subject: pgsql: Doesn't seem like a good idea to be doing AC_CHECK_SIZEOF(void *)