NotificationsYou must be signed in to change notification settings
Fork6
Star31

Commit9eecc8a

committed

Don't allow relminmxid to go backwards during VACUUM FULL

We were allowing a table's pg_class.relminmxid value to move backwardswhen heaps were swapped by VACUUM FULL or CLUSTER. There is asimilar protection against relfrozenxid going backwards, which weneglected to clone when the multixact stuff was rejiggered by commit0ac5ad5.Backpatch to 9.3, where relminmxid was introduced.As reported by Heikki inhttp://www.postgresql.org/message-id/52401AEA.9000608@vmware.com

1 parent4c888a6 commit9eecc8aCopy full SHA for 9eecc8a

File tree

1 file changed

-0

lines changed

src/backend/commands
- cluster.c

1 file changed

-0

lines changed

`‎src/backend/commands/cluster.c‎`

Lines changed: 6 additions & 0 deletions

Original file line number	Diff line number	Diff line change
`@@ -861,6 +861,12 @@ copy_heap_data(Oid OIDNewHeap, Oid OIDOldHeap, Oid OIDOldIndex, bool verbose,`
`861`	`861`	`if (TransactionIdPrecedes(FreezeXid,OldHeap->rd_rel->relfrozenxid))`
`862`	`862`	`FreezeXid=OldHeap->rd_rel->relfrozenxid;`
`863`	`863`
	`864`	`+/*`
	`865`	`+ * MultiXactCutoff, similarly, shouldn't go backwards either.`
	`866`	`+ */`
	`867`	`+if (MultiXactIdPrecedes(MultiXactCutoff,OldHeap->rd_rel->relminmxid))`
	`868`	`+MultiXactCutoff=OldHeap->rd_rel->relminmxid;`
	`869`	`+`
`864`	`870`	`/* return selected values to caller */`
`865`	`871`	`*pFreezeXid=FreezeXid;`
`866`	`872`	`*pCutoffMulti=MultiXactCutoff;`

0 commit comments

Comments

(0)

Movatterモバイル変換

Navigation Menu

Search code, repositories, users, issues, pull requests...

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Commit9eecc8a

File tree

1 file changed

1 file changed

`‎src/backend/commands/cluster.c‎`

0 commit comments