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

Vladimir Sitnikov <sitnikov.vladimir@gmail.com>

From: Vladimir Sitnikov <sitnikov.vladimir@gmail.com>

To: Kyotaro Horiguchi <horikyota.ntt@gmail.com>

Cc: Pgsql Hackers <pgsql-hackers@postgresql.org>, michael@paquier.xyz

Date: 2020-05-28T08:57:23Z

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

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

Fix crash in WAL sender when starting physical replication
- 10ffe0fa72ed 13.0 landed
- 879ad9f90e83 14.0 landed
Add a SHOW command to the replication command language.
- d1ecd539477f 10.0 cited