pgsql: When telling the bgwriter that we need a checkpoint because too - Mailing list pgsql-committers

From tgl@postgresql.org (Tom Lane)
Subject pgsql: When telling the bgwriter that we need a checkpoint because too
Date
Msg-id 20071012193959.335A7753E4C@cvs.postgresql.org
Whole thread Raw
List pgsql-committers
Log Message:
-----------
When telling the bgwriter that we need a checkpoint because too much xlog
has been consumed, recheck against the latest value of RedoRecPtr before
really sending the signal.  This avoids useless checkpoint activity if
XLogWrite is executed when we have a very stale local copy of RedoRecPtr.
The potential for useless checkpoint is very much worse in 8.3 because of
the walwriter process (which never does XLogInsert), so while this behavior
was intentional, it needs to be changed.  Per report from Itagaki Takahiro.

Modified Files:
--------------
    pgsql/src/backend/access/transam:
        xlog.c (r1.285 -> r1.286)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/transam/xlog.c?r1=1.285&r2=1.286)

pgsql-committers by date:

Previous
From: tgl@postgresql.org (Tom Lane)
Date:
Subject: pgsql: Remove hack in pg_tablespace_aclmask() that disallowed
Next
From: tgl@postgresql.org (Tom Lane)
Date:
Subject: pgsql: Teach planagg.c that partial indexes specifying WHERE foo IS NOT