]> granicus.if.org Git - postgresql/commit
projects / postgresql / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 4c888a6) | patch
Don't allow relminmxid to go backwards during VACUUM FULL
authorAlvaro Herrera <alvherre@alvh.no-ip.org>
Fri, 27 Jun 2014 18:43:46 +0000 (14:43 -0400)
committerAlvaro Herrera <alvherre@alvh.no-ip.org>
Fri, 27 Jun 2014 18:43:46 +0000 (14:43 -0400)
commit9eecc8a7cafa2be356a859f74c5db5961e190579
tree69b547d848d7c4840f9065eb029a5c49515cf18dtree | snapshot
parent4c888a6290add7ab86078c8759f0de1bd74c7377commit | 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 | history
Unnamed repository; edit this file 'description' to name the repository.