Horton

Re: Segfault logical replication PG 10.4

Mai Peng <maily.peng@webedia-group.com>

View thread View on postgr.es
From: Mai Peng <maily.peng@webedia-group.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>, pgsql-hackers@postgresql.org, maxence@bothorel.net
Date: 2018-07-19T10:20:18Z
Lists: pgsql-hackers 
Hello ,
Some new input:
On slave, all domains ( with checks) have been replaced by a simple type. No crash on slave since this bypass. 
Is there something to fix in the ActiveSnapshot code ?
BR


> Le 18 juil. 2018 à 17:03, Tom Lane <tgl@sss.pgh.pa.us> a écrit :
> 
> Mai Peng <maily.peng@webedia-group.com> writes:
>> Here the backtrace
> 
> Hmm .. so this can be summarized as "logical replication workers should
> provide an ActiveSnapshot in case the user functions they call want one".
> Makes me wonder how much other transactional infrastructure is needed
> but not present.
> 
> 			regards, tom lane

Commits

  1. Set ActiveSnapshot when logically replaying inserts