pgsql: When telling the bgwriter that we need a checkpoint because too

Поиск
Список
Период
Сортировка
От tgl@postgresql.org (Tom Lane)
Тема pgsql: When telling the bgwriter that we need a checkpoint because too
Дата
Msg-id 20071012193959.335A7753E4C@cvs.postgresql.org
обсуждение исходный текст
Список 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 по дате отправления:

Предыдущее
От: tgl@postgresql.org (Tom Lane)
Дата:
Сообщение: pgsql: Remove hack in pg_tablespace_aclmask() that disallowed
Следующее
От: tgl@postgresql.org (Tom Lane)
Дата:
Сообщение: pgsql: Teach planagg.c that partial indexes specifying WHERE foo IS NOT