Re: BUG #14758: Segfault with logical replication on a function index

From: Andres Freund <andres(at)anarazel(dot)de>
To: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
Cc: Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>, scott(at)deltaex(dot)com, pgsql-bugs <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: BUG #14758: Segfault with logical replication on a function index
Date: 2017-08-01 22:52:32
Message-ID: 20170801225232.csedyabn6rifsrx6@alap3.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-hackers

On 2017-08-01 16:28:31 -0400, Peter Eisentraut wrote:
> On 7/28/17 06:07, Masahiko Sawada wrote:
> > I could reproduced this issue and it seems to me that the cause of
> > this is that the table sync worker didn't get a snapshot before
> > starting table copy. Attached patch fixes this problem.
>
> Should it be GetTransactionSnapshot() rather than GetLatestSnapshot()?

Don't think it makes a meaningful difference here, but I agree it's more
consistent.

- Andres

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Masahiko Sawada 2017-08-02 01:23:24 Re: BUG #14758: Segfault with logical replication on a function index
Previous Message Peter Geoghegan 2017-08-01 20:42:33 Re: Crash report for some ICU-52 (debian8) COLLATE and work_mem values

Browse pgsql-hackers by date

  From Date Subject
Next Message Thomas Munro 2017-08-01 22:58:32 Why does logical replication launcher exit with exit code 1?
Previous Message Robert Haas 2017-08-01 22:25:38 Re: reload-through-the-top-parent switch the partition table