Re: Old row version in hot chain become visible after a freeze

Michael Paquier <michael.paquier@gmail.com>

From: Michael Paquier <michael.paquier@gmail.com>

To: Alvaro Herrera <alvherre@alvh.no-ip.org>

Cc: Peter Geoghegan <pg@bowt.ie>, "Wood, Dan" <hexpert@amazon.com>, "pgsql-bugs@postgresql.org" <pgsql-bugs@postgresql.org>, Andres Freund <andres@anarazel.de>, "Wong, Yi Wen" <yiwong@amazon.com>

Date: 2017-09-27T05:18:04Z

Lists: pgsql-bugs

On Sat, Sep 23, 2017 at 11:05 PM, Alvaro Herrera
<alvherre@alvh.no-ip.org> wrote:
> This fails in backbranches.  I think I should back-patch
> c2581794f37e ...

If you mean to merge those patches directly in the final versions to
be committed, yes that looks adapted.
-- 
Michael

Commits

Fix freezing of a dead HOT-updated tuple
- fb6de78a291b 9.5.10 landed
- d149aa762c05 9.3.20 landed
- 46c35116ae1a 10.0 landed
- 3a135bdb1b5e 9.6.6 landed
- 232c7cbcbbc6 9.4.15 landed
- 20b655224249 11.0 landed
Fix potential data corruption during freeze
- 31b8db8e6c1f 10.0 cited
Clarify the contract of partition_rbound_cmp().
- f1dae097f294 10.0 cited