VS: Re:Logical replication halted due to "this slot has been invalidated because it exceeded the maximum reserved size."
| От | Viljo Hakala |
|---|---|
| Тема | VS: Re:Logical replication halted due to "this slot has been invalidated because it exceeded the maximum reserved size." |
| Дата | |
| Msg-id | AS8PR05MB87412C3569BC7F47711B03CD97129@AS8PR05MB8741.eurprd05.prod.outlook.com обсуждение исходный текст |
| Ответ на | Re:Logical replication halted due to "this slot has been invalidated because it exceeded the maximum reserved size." (Sergei Kornilov <sk@zsrv.org>) |
| Список | pgsql-bugs |
HI,
Previously we had -1 as default for both of these instances and that caused same kind of issue.
Now we had set it to maximum value. We changed it back to -1
The logical replication was rebuilt over the weekend from scratch and issue occurred only 2-3 days after.
So we believe this is a bug. There seems to have been an issue in 13, that got fixed. But maybe this is a regression bug?
Regards,
Viljo
Lähettäjä: Sergei Kornilov <sk@zsrv.org>
Päivämäärä: tiistaina, 29. marraskuuta 2022 klo 15.16
Vastaanottaja: Alvaro Herrera <alvherre@alvh.no-ip.org>
Kopio: pgsql-bugs@lists.postgresql.org <pgsql-bugs@lists.postgresql.org>, Viljo Hakala <Viljo.Hakala@advania.com>
Aihe: Re:Logical replication halted due to "this slot has been invalidated because it exceeded the maximum reserved size."
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
В списке pgsql-bugs по дате отправления: