| From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
|---|---|
| To: | "Wong, Yi Wen" <yiwong(at)amazon(dot)com> |
| Cc: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Peter Geoghegan <pg(at)bowt(dot)ie>, "Wood, Dan" <hexpert(at)amazon(dot)com>, "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org>, Andres Freund <andres(at)anarazel(dot)de> |
| Subject: | Re: Old row version in hot chain become visible after a freeze |
| Date: | 2017-09-28 15:24:33 |
| Message-ID: | 20170928152433.x3hthukrhswom6xu@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Hmm. In going over this once more while looking at the coverage report
site, I wonder if the "NB" comment on top of heap_prepare_freeze_tuple
has important consequences for some of this new code. It probably does,
but I'm not sure what to do about it.
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David G. Johnston | 2017-09-28 15:27:28 | Re: Row security policies using session variable can be circumvented |
| Previous Message | Alvaro Herrera | 2017-09-28 15:00:29 | Re: Old row version in hot chain become visible after a freeze |