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: Amit Kapila <amit.kapila16@gmail.com>

Cc: pgsql-bugs mailing list <pgsql-bugs@postgresql.org>

Date: 2022-11-14T13:24:34Z

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, Nov 14, 2022 at 06:41:59PM +0530, Amit Kapila wrote:
> From the last two lines above, it is clear why it started working. The
> restart_lsn has advanced from 1039D/83825958 to 1039D/9170B010 which
> means the system no longer needs data from 000000010001039D00000083.

Sure, but how could it advance if the wal wasn't there?

Best regards,

depesz