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

From Andres Freund
Subject Re: BUG #15114: logical decoding Segmentation fault
Date
Msg-id 20181030230931.22pms35u3sqx4i7c@alap3.anarazel.de
Whole thread Raw
In response to Re: BUG #15114: logical decoding Segmentation fault  (Michael Paquier <michael@paquier.xyz>)
Responses Re: BUG #15114: logical decoding Segmentation fault  (Michael Paquier <michael@paquier.xyz>)
List pgsql-bugs
On 2018-10-31 08:07:36 +0900, Michael Paquier wrote:
> On Tue, Oct 30, 2018 at 08:45:57AM +0100, Petr Jelinek wrote:
> > The receiver side *should* actually use RelationGetIndexAttrBitmap, the
> > problem there seems to be rather than we setup snapshot few lines of
> > code too late in worker.c.
> 
> Does the worker need this much information though?  It just needs to
> know about the replication index itself and its columns, not about all
> the other indexes.  It may make sense to unify both code paths to behave
> similarly.

Replication needs to maintain the other indexes, and for that it needs
to evaluate predicates.  So I don't understand how you could say that it
doesn't need to know about other indexes?


Greetings,

Andres Freund


pgsql-bugs by date:

Previous
From: Michael Paquier
Date:
Subject: Re: BUG #15114: logical decoding Segmentation fault
Next
From: Andrew Gierth
Date:
Subject: Re: BUG #15467: The database subdirectory "pg_tblspc/1932420460/PG_10_201707211/16400" is missing.