Re: segmentation fault using currtid and partitioned tables - Mailing list pgsql-hackers

From Tom Lane
Subject Re: segmentation fault using currtid and partitioned tables
Date
Msg-id 11083.1590978414@sss.pgh.pa.us
Whole thread Raw
In response to Re: segmentation fault using currtid and partitioned tables  (Michael Paquier <michael@paquier.xyz>)
Responses Re: segmentation fault using currtid and partitioned tables
List pgsql-hackers
Michael Paquier <michael@paquier.xyz> writes:
> Woah.  This one is old, good catch from -DRELCACHE_FORCE_RELEASE.  It
> happens that since its introduction in a3519a2 from 2002,
> currtid_for_view() in tid.c closes the view and then looks at a RTE
> from it.  I have reproduced the issue and the patch attached takes
> care of the problem.  Would it be better to backpatch all the way down
> or is that not worth caring about?

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.

            regards, tom lane



pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: segmentation fault using currtid and partitioned tables
Next
From: Pavel Stehule
Date:
Subject: Re: Compatible defaults for LEAD/LAG