| From: | Scott Ribe <scott_ribe(at)elevated-dev(dot)com> |
|---|---|
| To: | Pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org> |
| Subject: | max_slot_wal_keep_size |
| Date: | 2021-08-16 13:58:17 |
| Message-ID: | 58D79C5B-B9FE-403B-97C0-40B6DF1E00CF@elevated-dev.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
If I use max_slot_wal_keep_size to limit disk impact of a down replica, and subsequently a down replica causes PG to hit this limit, is there a particular message that will be logged when the limit is crossed and PG starts to purge WAL?
Context is: trying to debug a failure to bring up a replica, where the failure happened in the middle of a moderately complex chain of events that likely started with a bad disk. (Patroni is involved, FWIW)
--
Scott Ribe
scott_ribe(at)elevated-dev(dot)com
https://www.linkedin.com/in/scottribe/
--
Scott Ribe
scott_ribe(at)elevated-dev(dot)com
https://www.linkedin.com/in/scottribe/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2021-08-16 14:08:56 | Re: max_slot_wal_keep_size |
| Previous Message | Ron | 2021-08-16 04:17:07 | Re: Join for the parent table will not leverage the index scan |