Re: [BUGS] Old row version in hot chain become visible after a freeze - Mailing list pgsql-bugs

From Alvaro Herrera
Subject Re: [BUGS] Old row version in hot chain become visible after a freeze
Date
Msg-id 20170906132738.2dpwvnfcuevjofhl@alvherre.pgsql
Whole thread Raw
In response to Re: [BUGS] Old row version in hot chain become visible after a freeze  (Michael Paquier <michael.paquier@gmail.com>)
Responses Re: [BUGS] Old row version in hot chain become visible after a freeze
Re: [BUGS] Old row version in hot chain become visible after a freeze
List pgsql-bugs
Another thing is that if you're going through heap_copy_data, the tuple
is only checked for DEAD, not RECENTLY_DEAD.  Maybe there is no bug here
but I'm not sure yet.

I attach the patch as I have it now -- mostly comment tweaks, but also
the change to not mark page as all-frozen when we skip freezing a
recently read tuple.  I also renamed the test case, because I think it
may be possible to reach the problem code without involving a multixact.
Haven't tried too hard though.

-- 
Álvaro Herrera                https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

-- 
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs

Attachment

pgsql-bugs by date:

Previous
From: kostin.artem@gmail.com
Date:
Subject: [BUGS] BUG #14800: substring produces different results with similar types
Next
From: Tom Lane
Date:
Subject: Re: [BUGS] BUG #14799: SELECT * FROM transition_table in a statement-level trigger