Re: pgsql: Fix "base" snapshot handling in logical decoding
Arseny Sher <a.sher@postgrespro.ru>
From: Arseny Sher <a.sher@postgrespro.ru>
To: Alvaro Herrera <alvherre@2ndquadrant.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, pgsql-hackers@lists.postgresql.org
Date: 2018-07-06T07:55:41Z
Lists: pgsql-hackers
Alvaro Herrera <alvherre@2ndquadrant.com> writes:
> I just don't see it that VACUUM FULL would change the xmin of anything
> to FrozenXid, and in my experiments it doesn't. Did you mean VACUUM
> FREEZE?
Well, docs for VACUUM say:
FREEZE
Selects aggressive “freezing” of tuples. Specifying FREEZE is
equivalent to performing VACUUM with the vacuum_freeze_min_age and
vacuum_freeze_table_age parameters set to zero. Aggressive freezing
is always performed when the table is rewritten, so this option is
redundant when FULL is specified.
So this is literally the same. rewrite_heap_tuple does the job.
> Thanks for the detective work! I pushed this test change.
Thank you, I appreciate this.
--
Arseny Sher
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company
Commits
-
Reduce cost of test_decoding's new oldest_xmin test
- 7acbb481c808 10.5 landed
- 301b2a1aad77 9.6.10 landed
- eedbbff504e4 9.5.14 landed
- aba2184bed64 11.0 landed
- 8d1c1ca70b01 12.0 landed
-
Fix "base" snapshot handling in logical decoding
- f49a80c481f7 11.0 cited