Re: Segfault logical replication PG 10.4

From: Mai Peng <maily(dot)peng(at)webedia-group(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, pgsql-hackers(at)postgresql(dot)org, maxence(at)bothorel(dot)net
Subject: Re: Segfault logical replication PG 10.4
Date: 2018-07-19 10:20:18
Message-ID: D1AA9B3B-C417-4967-B0E0-896482AA5D49@webedia-group.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
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(at)sss(dot)pgh(dot)pa(dot)us> a écrit :
>
> Mai Peng <maily(dot)peng(at)webedia-group(dot)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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Kyotaro HORIGUCHI 2018-07-19 10:30:54 Re: [HACKERS] PATCH: Keep one postmaster monitoring pipe per process
Previous Message Heikki Linnakangas 2018-07-19 09:38:58 Re: [PATCH] Find additional connection service files in pg_service.conf.d directory