pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
BUG #18792: Segmentaion Fault error when changing new parameter synchronized_standby_slots
2+ messages / 2 participants
[nested] [flat]

* BUG #18792: Segmentaion Fault error when changing new parameter synchronized_standby_slots
@ 2025-02-03 17:03 PG Bug reporting form <noreply@postgresql.org>
  2025-02-03 23:05 ` Re: BUG #18792: Segmentaion Fault error when changing new parameter synchronized_standby_slots Tom Lane <tgl@sss.pgh.pa.us>
  0 siblings, 1 reply; 2+ messages in thread

From: PG Bug reporting form @ 2025-02-03 17:03 UTC (permalink / raw)
  To: pgsql-bugs@lists.postgresql.org; +Cc: a.glushakov86@gmail.com

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



^ permalink  raw  reply  [nested|flat] 2+ messages in thread

* Re: BUG #18792: Segmentaion Fault error when changing new parameter synchronized_standby_slots
  2025-02-03 17:03 BUG #18792: Segmentaion Fault error when changing new parameter synchronized_standby_slots PG Bug reporting form <noreply@postgresql.org>
@ 2025-02-03 23:05 ` Tom Lane <tgl@sss.pgh.pa.us>
  0 siblings, 0 replies; 2+ messages in thread

From: Tom Lane @ 2025-02-03 23:05 UTC (permalink / raw)
  To: a.glushakov86@gmail.com; +Cc: pgsql-bugs@lists.postgresql.org

PG Bug reporting form <noreply@postgresql.org> writes:
> 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

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





^ permalink  raw  reply  [nested|flat] 2+ messages in thread


end of thread, other threads:[~2025-02-03 23:05 UTC | newest]

Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2025-02-03 17:03 BUG #18792: Segmentaion Fault error when changing new parameter synchronized_standby_slots PG Bug reporting form <noreply@postgresql.org>
2025-02-03 23:05 ` Tom Lane <tgl@sss.pgh.pa.us>

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