BUG #18792: Segmentaion Fault error when changing new parameter synchronized_standby_slots

Started by PG Bug reporting formabout 1 year ago2 messagesbugs
Jump to latest
#1PG Bug reporting form
noreply@postgresql.org

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.
/messages/by-id/202411281216.sutbxtr6idnn@alvherre.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

#2Tom Lane
tgl@sss.pgh.pa.us
In reply to: PG Bug reporting form (#1)
Re: BUG #18792: Segmentaion Fault error when changing new parameter synchronized_standby_slots

PG Bug reporting form <noreply@postgresql.org> writes:

I found a discussion of the problem, but it seems that it was not solved.
/messages/by-id/202411281216.sutbxtr6idnn@alvherre.pgsql

That discussion began on 2024-11-28, and the fix was pushed a few days
later. It would require time travel for the fix to have been in 17.2
(released 2024-11-21). Should be in next week's 17.3, though.

regards, tom lane