]> granicus.if.org Git - postgresql/commit
projects / postgresql / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: b277057) | 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)
commitb7e51d9c06e6a0da50abbbd0603ecb80f0b6f02b
treeb62a6827f4379d97f079ec9bcf71ea96b5990da3tree | snapshot
parentb2770576486265c2ce35b64e875028672a3bb7b5commit | 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.