Re: pgsql: Fix "base" snapshot handling in logical decoding - Mailing list pgsql-hackers

From Arseny Sher
Subject Re: pgsql: Fix "base" snapshot handling in logical decoding
Date
Msg-id 87muv4iyrm.fsf@ars-thinkpad
Whole thread Raw
In response to Re: pgsql: Fix "base" snapshot handling in logical decoding  (Alvaro Herrera <alvherre@2ndquadrant.com>)
List 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


pgsql-hackers by date:

Previous
From: Alexander Lakhin
Date:
Subject: Re: make installcheck-world in a clean environment
Next
From: Pavel Stehule
Date:
Subject: small doc fix - using expressions in plpgsql FETCH command