Try
Home   >   mailing lists

pgsql: Don't try to truncate multixact SLRU files in checkpoints done - Mailing list pgsql-committers

From [email protected] (Tom Lane)
Subject pgsql: Don't try to truncate multixact SLRU files in checkpoints done
Date
Msg-id [email protected]
Whole thread Raw
List pgsql-committers
Tree view 
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:

Previous
From: [email protected] (User Gsmet)
Date:
Subject: pgfouine - pgfouine: more work on vacuum verbose output analysis
Next
From: [email protected] (Tom Lane)
Date:
Subject: pgsql: Don't try to truncate multixact SLRU files in checkpoints done