RE: error “server process was terminated by signal 11: Segmentation fault” running pg_create_logical_replication_slot using pgoutput plugin - Mailing list pgsql-general

From Hayato Kuroda (Fujitsu)
Subject RE: error “server process was terminated by signal 11: Segmentation fault” running pg_create_logical_replication_slot using pgoutput plugin
Date
Msg-id OS7PR01MB14968C27D3E6D1EE9E5F5AB97F548A@OS7PR01MB14968.jpnprd01.prod.outlook.com
Whole thread Raw
In response to Re: error “server process was terminated by signal 11: Segmentation fault” running pg_create_logical_replication_slot using pgoutput plugin  (Shlok Kyal <shlok.kyal.oss@gmail.com>)
List pgsql-general
Dear Shlok, Abrahim,

> Also, I was going to the logs on found:
> > > < 2025-07-08 14:57:08.653 UTC psql postgres postgres 172.18.0.94(53414)
> SELECT 00000 2025-07-08 14:57:07 UTC 1096 686d31c3.448 2025-07-08
> 14:57:08.653 UTC > LOG:  Initializing CDC decoder
>
> This log is not present in Postgres source code. Why is this log appearing here?

I found the output in Citus source code [1]. So, I'm afraid that you may load the
shared library provided by Citus when you created the replication slot.

If so, Citus community may be the better place to discuss the bug.
We can help if you can reproduce the bug by the PostgreSQL core codes.

[1]:
https://github.com/citusdata/citus/blob/5deaf9a61673e10c183b6d4f13593f168e1c2c10/src/backend/distributed/cdc/cdc_decoder.c#L85

Best regards,
Hayato Kuroda
FUJITSU LIMITED




pgsql-general by date:

Previous
From: Peter Geoghegan
Date:
Subject: Re: Corrupt btree index includes rows that don't match
Next
From: Dominique Devienne
Date:
Subject: Aggregate versions of hashing functions (md5, sha1, etc...)