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

From Michael Paquier
Subject Re: segmentation fault using currtid and partitioned tables
Date
Msg-id 20200601022055.GB4121@paquier.xyz
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
On Mon, Jun 01, 2020 at 10:57:29AM +0900, Michael Paquier wrote:
> Applied this one then.  I also got to check the ODBC driver in more
> details, and I am indeed not seeing those functions getting used.
> One extra thing to know is that the ODBC driver requires libpq from at
> least 9.2, which may give one more argument to just remove them.
>
> NB: prion has been failing, just looking into it.

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?
--
Michael

Attachment

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Compatible defaults for LEAD/LAG
Next
From: Tom Lane
Date:
Subject: Re: segmentation fault using currtid and partitioned tables