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 20200526025959.GE6155@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
Re: segmentation fault using currtid and partitioned tables
List pgsql-hackers
On Mon, May 25, 2020 at 06:29:10PM +0900, Michael Paquier wrote:
> Perhaps you are right though, and that we don't need to spend this
> much energy into improving the error messages so I am fine to discard
> this part.  At the end, in order to remove the crashes, you just need
> to keep around the two RELKIND_HAS_STORAGE() checks.  But I would
> rather keep these two to use ereport(ERRCODE_FEATURE_NOT_SUPPORTED)
> instead of elog(), and keep the test coverage of the previous patch
> (including the tests for the aggregates I noticed were missing).
> Would you be fine with that?

And this means the attached.  Thoughts are welcome.
--
Michael

Attachment

pgsql-hackers by date:

Previous
From: "Nikolay Samokhvalov"
Date:
Subject: Re: Default gucs for EXPLAIN
Next
From: Laurenz Albe
Date:
Subject: Re: Default gucs for EXPLAIN