Re: BUG #15114: logical decoding Segmentation fault - Mailing list pgsql-bugs

From Michael Paquier
Subject Re: BUG #15114: logical decoding Segmentation fault
Date
Msg-id 20190129075941.GH3121@paquier.xyz
Whole thread Raw
In response to Re: BUG #15114: logical decoding Segmentation fault  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
Responses Re: BUG #15114: logical decoding Segmentation fault
List pgsql-bugs
On Mon, Jan 28, 2019 at 10:32:16PM +0100, Peter Eisentraut wrote:
> My approach is to make RelationGetIndexAttrBitmap() not need a snapshot.
>  The whole code was overly complicated anyway, calling BuildIndexInfo()
> and then throwing the result away.  We can do it directly more
> efficiently and avoid all the business about eval_const_expressions().
> Moreover, this fixes the problem in a central place and does not require
> bespoke separate fixes in the publisher and subscriber code.  External
> logical decoding or logical replication implementations could also be
> affected and would benefit from this fix.

I have spent some time for the last couple of days looking at this
patch, and that's a neat approach.

+        * those might run constants evaluation, which needs a snapshot, which
"constants evaluation" sounds like weird English.  "constant
evaluation" or "evaluation of constants would be better"?

Thanks for adding a test case as well, Peter.
--
Michael

Attachment

pgsql-bugs by date:

Previous
From: Andrew Gierth
Date:
Subject: Re: BUG #15609: synchronous_commit=off insert performance regression with secondary indexes
Next
From: Sandeep Thakkar
Date:
Subject: Re: BUG #15564: Setup sets wrong data type for value in Windows Registry