| From: | Peter Geoghegan <pg(at)bowt(dot)ie> |
|---|---|
| To: | "Wood, Dan" <hexpert(at)amazon(dot)com> |
| Cc: | "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: Old row version in hot chain become visible after a freeze |
| Date: | 2017-09-01 03:25:25 |
| Message-ID: | CAH2-Wz=75ak_0evvFegjcPsk1kBRsGoN0qkY44u_u5HZeg4YZA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Thu, Aug 31, 2017 at 3:36 PM, Wood, Dan <hexpert(at)amazon(dot)com> wrote:
> I’ve found a bug in Postgres which causes old row versions to appear in a
> table. DEAD rows in a hot chain are getting frozen and becoming visible.
> I’ve repro’d this in both 9.6.1 and 11-devel.
I can confirm that this goes all the way back to 9.3, where "for key
share"/foreign key locks were introduced.
--
Peter Geoghegan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2017-09-01 03:46:44 | Re: Old row version in hot chain become visible after a freeze |
| Previous Message | Peter Geoghegan | 2017-09-01 00:07:39 | Re: Old row version in hot chain become visible after a freeze |