| From: | Sergei Kornilov <sk(at)zsrv(dot)org> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
| Cc: | pgsql-bugs(at)lists(dot)postgresql(dot)org, Viljo Hakala <viljo(dot)hakala(at)advania(dot)com> |
| Subject: | Re:Logical replication halted due to "this slot has been invalidated because it exceeded the maximum reserved size." |
| Date: | 2022-11-29 13:16:40 |
| Message-ID: | 2263571669727800@mks45hieef2apcju.myt.yp-c.yandex.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin pgsql-bugs |
Hello
> The only explanation of this behavior that doesn't involve a bug is that
this parameter was set to a nonzero value, then set to disabled, but the
checkpointer failed to notice the change.
Or max_slot_wal_keep_size is really set on the publication database, but only the subscription database config was checked.
regards, Sergei
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Viljo Hakala | 2022-11-29 13:44:29 | VS: Re:Logical replication halted due to "this slot has been invalidated because it exceeded the maximum reserved size." |
| Previous Message | Alvaro Herrera | 2022-11-29 09:41:49 | Re: Logical replication halted due to "this slot has been invalidated because it exceeded the maximum reserved size." |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Viljo Hakala | 2022-11-29 13:44:29 | VS: Re:Logical replication halted due to "this slot has been invalidated because it exceeded the maximum reserved size." |
| Previous Message | Daniel Gustafsson | 2022-11-29 11:31:08 | Re: BUG #17702: An assert failed in parse_utilcmd.c |