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

pgsql: Don't try to truncate multixact SLRU files in checkpoints done

From: tgl(at)postgresql(dot)org (Tom Lane)
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Don't try to truncate multixact SLRU files in checkpoints done
Date: 2006-07-20 00:46:42
Message-ID: 20060720004643.0131E9FA64B@postgresql.org (view raw or flat)
Thread:
Lists: pgsql-committers
Log Message:
-----------
Don't try to truncate multixact SLRU files in checkpoints done during xlog
recovery.  In the first place, it doesn't work because slru's
latest_page_number isn't set up yet (this is why we've been hearing reports
of strange "apparent wraparound" log messages during crash recovery, but
only from people who'd managed to advance their next-mxact counters some
considerable distance from 0).  In the second place, it seems a bit unwise
to be throwing away data during crash recovery anwyway.  This latter
consideration convinces me to just disable truncation during recovery,
rather than computing latest_page_number and pushing ahead.

Modified Files:
--------------
    pgsql/src/backend/access/transam:
        multixact.c (r1.19 -> r1.20)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/transam/multixact.c.diff?r1=1.19&r2=1.20)

pgsql-committers by date

Next:From: Tom LaneDate: 2006-07-20 00:46:56
Subject: pgsql: Don't try to truncate multixact SLRU files in checkpoints done
Previous:From: User GsmetDate: 2006-07-19 22:55:04
Subject: pgfouine - pgfouine: more work on vacuum verbose output analysis

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