Re: WAL segments removed from primary despite the fact that logical replication slot needs it.
hubert depesz lubaczewski <depesz@depesz.com>
From: hubert depesz lubaczewski <depesz@depesz.com>
To: Andres Freund <andres@anarazel.de>
Cc: Masahiko Sawada <sawada.mshk@gmail.com>, Amit Kapila <amit.kapila16@gmail.com>, pgsql-bugs mailing list <pgsql-bugs@postgresql.org>
Date: 2022-11-18T11:27:17Z
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 →
-
Fix a possibility of logical replication slot's restart_lsn going backwards.
- e5ed873b1b4a 18.0 landed
- 568e78a653ee 17.2 landed
- f353911337cf 16.6 landed
- 91771b3fbbc3 15.10 landed
- 26c4e8968690 14.15 landed
- 15dc1abb17dd 13.18 landed
On Thu, Nov 17, 2022 at 10:55:29AM -0800, Andres Freund wrote: > Hi, > > On 2022-11-17 23:22:12 +0900, Masahiko Sawada wrote: > > On Thu, Nov 17, 2022 at 5:03 PM Andres Freund <andres@anarazel.de> wrote: > > > > > 4. wal sender restarts for some reason (or server crashed). > > > > > > I don't think walsender alone restarting should change anything, but > > > crash-restart obviously would. > > > > Right. I've confirmed this scenario is possible to happen with crash-restart. > > Depesz, were there any crashes / immediate restarts on the PG 12 side? If so, > then we know what the problem likely is and can fix it. If not... > > > Just to confirm, the problem has "newly" occurred after you've upgraded to > 12.12? I couldn't quite tell from the thread. No crashes that I can find any track of. And no, it's not related to 12.12 We were using 12.9, and in process of trying to figure stuff out we upgraded to 12.12, which didn't help. Best regards, depesz