Postgres Pro
Downloads
Home   >   mailing lists

RE: incorrect wal removal due to max_slot_wal_keep_size - Mailing list pgsql-hackers

From Hayato Kuroda (Fujitsu)
Subject RE: incorrect wal removal due to max_slot_wal_keep_size
Date
Msg-id TYAPR01MB56927540236C5618DDF88355F5782@TYAPR01MB5692.jpnprd01.prod.outlook.com
Whole thread Raw
In response to incorrect wal removal due to max_slot_wal_keep_size  (Jeff Janes <jeff.janes@gmail.com>)
List pgsql-hackers
Tree view 
Dear Jeff,

Thanks for reporting the issue. I've tried to reproduce the issue (by adding delay
on worker-side and immediate shut-down), but not done yet. If possible, could you
please share a script to reproduce? It is helpful to analyze.

> I'm going to try to reproduce this on 17.0, but in the meantime any other suggestions for investigating this?x

It is very helpful to check the content of pg_stat_replication_slots view and pg_wal
directory of the postgres, when you succeed to reproduce. Also, please set
log_min_messages = DEBUG2 to check logs from RemoveOldXlogFiles() and RemoveXlogFile().
I want to see the log when you can reproduce.

They are inspired by [1]. I doubt the thread and yours are the same issue or not.

[1]: https://www.postgresql.org/message-id/flat/Yz2hivgyjS1RfMKs%40depesz.com

Best regards,
Hayato Kuroda
FUJITSU LIMITED

pgsql-hackers by date:

Previous
From: Aleksander Alekseev
Date:
Subject: Re: Build issue with postgresql 17 undefined reference to `pg_encoding_to_char' and `pg_char_to_encoding'
Next
From: Christoph Moench-Tegeder
Date:
Subject: Re: sunsetting md5 password support