pgsql: Don't allow relminmxid to go backwards during VACUUM FULL

Поиск
Список
Период
Сортировка
От Alvaro Herrera
Тема pgsql: Don't allow relminmxid to go backwards during VACUUM FULL
Дата
Msg-id E1X0bAb-000858-3t@gemulon.postgresql.org
обсуждение исходный текст
Список pgsql-committers
Don't allow relminmxid to go backwards during VACUUM FULL

We were allowing a table's pg_class.relminmxid value to move backwards
when heaps were swapped by VACUUM FULL or CLUSTER.  There is a
similar protection against relfrozenxid going backwards, which we
neglected to clone when the multixact stuff was rejiggered by commit
0ac5ad5134f276.

Backpatch to 9.3, where relminmxid was introduced.

As reported by Heikki in
http://www.postgresql.org/message-id/52401AEA.9000608@vmware.com

Branch
------
REL9_3_STABLE

Details
-------
http://git.postgresql.org/pg/commitdiff/e86cfc4bbe198f8c7367e8b23efadae97da64d7c

Modified Files
--------------
src/backend/commands/cluster.c |    6 ++++++
1 file changed, 6 insertions(+)


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

Предыдущее
От: Alvaro Herrera
Дата:
Сообщение: pgsql: Fix broken Assert() introduced by 8e9a16ab8f7f0e58
Следующее
От: Tom Lane
Дата:
Сообщение: pgsql: Allow pushdown of WHERE quals into subqueries with window functi