Re: segmentation fault using currtid and partitioned tables

Michael Paquier <michael@paquier.xyz>

From: Michael Paquier <michael@paquier.xyz>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Andres Freund <andres@anarazel.de>, Alvaro Herrera <alvherre@2ndquadrant.com>, Jaime Casanova <jaime.casanova@2ndquadrant.com>, Pg Hackers <pgsql-hackers@postgresql.org>
Date: 2020-06-01T05:55:27Z
Lists: pgsql-hackers
On Sun, May 31, 2020 at 10:26:54PM -0400, Tom Lane wrote:
> Ugh.  Aside from the stale-pointer-deref problem, once we drop the lock
> we can't even be sure the table still exists.  +1 for back-patch.

Thanks.  Fixed down to 9.5 then to make prion happier.
--
Michael

Commits

  1. Fix use-after-release mistake in currtid() and currtid2() for views

  2. Fix crashes with currtid() and currtid2()