projects / postgresql.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 5c53844) | patch
Don't allow relminmxid to go backwards during VACUUM FULL
authorAlvaro Herrera <alvherre@alvh.no-ip.org>
Fri, 27 Jun 2014 18:43:45 +0000 (14:43 -0400)
committerAlvaro Herrera <alvherre@alvh.no-ip.org>
Fri, 27 Jun 2014 18:43:45 +0000 (14:43 -0400)
commite86cfc4bbe198f8c7367e8b23efadae97da64d7c
treecd22d325b1855d9e81d6df9805bf5f61110c20a5tree
parent5c538442a0a73b9d4f3fa11ecac6d5b93a982acacommit | diff
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
src/backend/commands/cluster.c diff | blob | blame | history
This is the main PostgreSQL git repository.