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

Поиск
Список
Период
Сортировка
От tgl@postgresql.org (Tom Lane)
Тема pgsql: Don't try to truncate multixact SLRU files in checkpoints done
Дата
Msg-id 20060720004656.E14AF9FA64B@postgresql.org
обсуждение исходный текст
Список 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.

Tags:
----
REL8_1_STABLE

Modified Files:
--------------
    pgsql/src/backend/access/transam:
        multixact.c (r1.11.2.1 -> r1.11.2.2)

(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/transam/multixact.c.diff?r1=1.11.2.1&r2=1.11.2.2)

В списке pgsql-committers по дате отправления:

Предыдущее
От: tgl@postgresql.org (Tom Lane)
Дата:
Сообщение: pgsql: Don't try to truncate multixact SLRU files in checkpoints done
Следующее
От: tgl@postgresql.org (Tom Lane)
Дата:
Сообщение: pgsql: Make pg_regress.c get paths from pg_config_paths.h, instead of -D