| From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
|---|---|
| To: | pgsql-committers(at)postgresql(dot)org |
| Subject: | pgsql: Don't allow relminmxid to go backwards during VACUUM FULL |
| Date: | 2014-06-27 18:46:45 |
| Message-ID: | E1X0bAb-000858-3t@gemulon.postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
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
Branch
------
REL9_3_STABLE
Details
-------
http://git.postgresql.org/pg/commitdiff/e86cfc4bbe198f8c7367e8b23efadae97da64d7c
Modified Files
--------------
src/backend/commands/cluster.c | 6 ++++++
1 file changed, 6 insertions(+)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2014-06-28 06:08:05 | pgsql: Allow pushdown of WHERE quals into subqueries with window functi |
| Previous Message | Tom Lane | 2014-06-27 18:09:06 | pgsql: Disallow pushing volatile qual expressions down into DISTINCT su |