Horton

VS: Re:Logical replication halted due to "this slot has been invalidated because it exceeded the maximum reserved size."

Viljo Hakala <viljo.hakala@advania.com>

View thread
From: Viljo Hakala <Viljo.Hakala@advania.com>
To: Sergei Kornilov <sk@zsrv.org>, Alvaro Herrera <alvherre@alvh.no-ip.org>
Cc: "pgsql-bugs@lists.postgresql.org" <pgsql-bugs@lists.postgresql.org>
Date: 2022-11-29T13:44:29Z
Lists: pgsql-bugs

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Advance old-segment horizon properly after slot invalidation

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?

https://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=866237a6fa01a128325df41ad39b41ea3363c9a9


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