diff options
| author | Alvaro Herrera <alvherre@alvh.no-ip.org> | 2014-06-27 14:43:46 -0400 |
|---|---|---|
| committer | Alvaro Herrera <alvherre@alvh.no-ip.org> | 2014-06-27 14:43:46 -0400 |
| commit | b7e51d9c06e6a0da50abbbd0603ecb80f0b6f02b (patch) | |
| tree | b62a6827f4379d97f079ec9bcf71ea96b5990da3 | |
| parent | b2770576486265c2ce35b64e875028672a3bb7b5 (diff) | |
| download | postgresql-b7e51d9c06e6a0da50abbbd0603ecb80f0b6f02b.tar.gz postgresql-b7e51d9c06e6a0da50abbbd0603ecb80f0b6f02b.zip | |
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
| -rw-r--r-- | src/backend/commands/cluster.c | 6 |
1 files changed, 6 insertions, 0 deletions
diff --git a/src/backend/commands/cluster.c b/src/backend/commands/cluster.c index 54a27531825..b1c411a0b96 100644 --- a/src/backend/commands/cluster.c +++ b/src/backend/commands/cluster.c @@ -861,6 +861,12 @@ copy_heap_data(Oid OIDNewHeap, Oid OIDOldHeap, Oid OIDOldIndex, bool verbose, if (TransactionIdPrecedes(FreezeXid, OldHeap->rd_rel->relfrozenxid)) FreezeXid = OldHeap->rd_rel->relfrozenxid; + /* + * MultiXactCutoff, similarly, shouldn't go backwards either. + */ + if (MultiXactIdPrecedes(MultiXactCutoff, OldHeap->rd_rel->relminmxid)) + MultiXactCutoff = OldHeap->rd_rel->relminmxid; + /* return selected values to caller */ *pFreezeXid = FreezeXid; *pCutoffMulti = MultiXactCutoff; |