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: Kyotaro Horiguchi <horikyota.ntt@gmail.com>
Cc: amit.kapila16@gmail.com, pgsql-bugs@postgresql.org
Date: 2022-10-17T09:14:32Z
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 Mon, Oct 17, 2022 at 03:53:07PM +0900, Kyotaro Horiguchi wrote: > Anyway, I didn't come up with a possibility other than of someone else > having removed those files.. For example, virus scan softwares. If > any such software kills processes that is grabbing the files that the > software identified as malicious and is going to remove, that could be > happen? We don't use virus scanning there. The pg12 server is on ubuntu 18.04, used for normal production workload, and pg14 is on ubuntu focal, with no load, aside from 2 physical streaming replication to pg14 replicas. Best regards, depesz