From: PG Bug reporting form <noreply@postgresql.org>
To: pgsql-bugs@lists.postgresql.org
Cc: a.glushakov86@gmail.com
Subject: BUG #18792: Segmentaion Fault error when changing new parameter synchronized_standby_slots
Date: Mon, 03 Feb 2025 17:03:32 +0000
Message-ID: <18792-1d848ad538b1033c@postgresql.org> (raw)
The following bug has been logged on the website:
Bug reference: 18792
Logged by: Anton Glushakov
Email address: a.glushakov86@gmail.com
PostgreSQL version: 17.2
Operating system: AlmaLinux 9.5
Description:
I found a discussion of the problem, but it seems that it was not solved.
https://www.postgresql.org/message-id/flat/202411281216.sutbxtr6idnn%40alvherre.pgsql
It's still reproduce.
postgres=# alter system set synchronized_standby_slots='standby_slot';
ALTER SYSTEM
postgres=# select pg_reload_conf();
pg_reload_conf
----------------
t
(1 row)
postgres=#
\q
$ tail log/postgresql-Mon.log
2025-02-03 19:53:50.656 MSK [1098967] LOG: received SIGHUP, reloading
configuration files
2025-02-03 19:53:50.657 MSK [1098967] LOG: parameter
"synchronized_standby_slots" changed to "standby_slot"
2025-02-03 19:53:50.725 MSK [1098967] LOG: system logger process (PID
1098968) was terminated by signal 11: Segmentation fault
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: noreply@postgresql.org, pgsql-bugs@lists.postgresql.org, a.glushakov86@gmail.com
Subject: Re: BUG #18792: Segmentaion Fault error when changing new parameter synchronized_standby_slots
In-Reply-To: <18792-1d848ad538b1033c@postgresql.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox