Re: SIGSEGV from START_REPLICATION 0/XXXXXXX in XLogSendPhysical () at walsender.c:2762

From: Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>
To: michael(at)paquier(dot)xyz
Cc: sitnikov(dot)vladimir(at)gmail(dot)com, pgsql-hackers(at)postgresql(dot)org
Subject: Re: SIGSEGV from START_REPLICATION 0/XXXXXXX in XLogSendPhysical () at walsender.c:2762
Date: 2020-05-28 07:32:22
Message-ID: 20200528.163222.1462853998645356817.horikyota.ntt@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

At Thu, 28 May 2020 16:22:33 +0900, Michael Paquier <michael(at)paquier(dot)xyz> wrote in
> On Thu, May 28, 2020 at 09:07:04AM +0300, Vladimir Sitnikov wrote:
> > The CI history shows that HEAD was good at 11 May 13:27 UTC, and it became
> > bad by 19 May 14:00 UTC,
> > so the regression was introduced somewhere in-between.
> >
> > Does that ring any bells?
>
> It does, thanks! This would map with 1d374302 or 850196b6 that
> reworked this area of the code, so it seems like we are not quite done
> with this work yet. Do you still see the problem as of 55ca50d
> (today's latest HEAD)?

I think that's not the case. I think I cause this crash with the
HEAD. I'll post a fix soon.

> Also, just wondering.. If I use more or less the same commands as
> your travis job I should be able to reproduce the problem with a fresh
> JDBC repository, right? Or do you a sub-portion of your regression
> tests to run that easily?

Pgjdbc seems initiating physical replication on a logical replication
session.

regards.

--
Kyotaro Horiguchi
NTT Open Source Software Center

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2020-05-28 07:44:06 Re: WAL reader APIs and WAL segment open/close callbacks
Previous Message Dilip Kumar 2020-05-28 07:27:29 Re: PATCH: logical_work_mem and logical streaming of large in-progress transactions