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

From Noah Misch
Subject Re: BUG #15114: logical decoding Segmentation fault
Date
Msg-id 20190129015350.GA4128278@rfd.leadboat.com
Whole thread Raw
In response to Re: BUG #15114: logical decoding Segmentation fault  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
List pgsql-bugs
Looks good.  I found no functional problems.

On Mon, Jan 28, 2019 at 10:32:16PM +0100, Peter Eisentraut wrote:
> The fix is to avoid the constant expressions simplification in
> RelationGetIndexAttrBitmap(), so that it becomes safe to call in these
> contexts.  The constant expressions simplification comes from the
> calls to RelationGetIndexExpressions()/RelationGetIndexPredicate() via
> BuildIndexInfo().  But RelationGetIndexAttrBitmap() calling
> BuildIndexInfo() is overkill.  The latter just takes pg_index catalog
> information, packs it into the IndexInfo structure, which former than
> just unpacks again and throws away.

s/former than/the former then/


pgsql-bugs by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: BUG #15114: logical decoding Segmentation fault
Next
From: PG Bug reporting form
Date:
Subject: BUG #15609: synchronous_commit=off insert performance regression with secondary indexes