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

From: Vladimir Sitnikov <sitnikov(dot)vladimir(at)gmail(dot)com>
To: Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>
Cc: Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org>, michael(at)paquier(dot)xyz
Subject: Re: SIGSEGV from START_REPLICATION 0/XXXXXXX in XLogSendPhysical () at walsender.c:2762
Date: 2020-05-28 08:57:23
Message-ID: CAB=Je-HnFcwPUeLq5CXUqBnC7G7WeTi7DdGKbnFe-EizvnBJmw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Kyotaro>It seems to me that that crash means Pgjdbc is initiating a logical
Kyotaro>replication connection to start physical replication.

Well, it used to work previously, so it might be a breaking change from the
client/application point of view.

Vladimir

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Pavel Stehule 2020-05-28 09:08:27 Re: Inlining of couple of functions in pl_exec.c improves performance
Previous Message Kyotaro Horiguchi 2020-05-28 08:09:25 Re: max_slot_wal_keep_size comment in postgresql.conf