Re: Newly created replication slot may be invalidated by checkpoint

suyu.cmj <mengjuan.cmj@alibaba-inc.com>

From: 蔡梦娟(玊于) <mengjuan.cmj@alibaba-inc.com>

To: "Amit Kapila" <amit.kapila16@gmail.com>

Cc: "aekorotkov" <aekorotkov@gmail.com>, "tomas" <tomas@vondra.me>, "v.davydov" <v.davydov@postgrespro.ru>, "michael" <michael@paquier.xyz>, "bharath.rupireddyforpostgres" <bharath.rupireddyforpostgres@gmail.com>, "pgsql-hackers" <pgsql-hackers@postgresql.org>

Date: 2025-09-23T15:08:12Z

Lists: pgsql-hackers

Commits

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

Prevent invalidation of newly synced replication slots.
- 3243c0177efb 17.8 landed
- 919c9fa13cd0 18.2 landed
- 851f6649cc18 19 (unreleased) landed
Prevent invalidation of newly created replication slots.
- 3510ebeb0dfa 17.8 landed
- 24cce33c332a 16.12 landed
- aae05622a7cb 15.16 landed
- 7406df60569f 14.21 landed
- d3ceb20846e4 18.2 landed
- 006dd4b2e5b3 19 (unreleased) landed
Fix re-distributing previously distributed invalidation messages during logical decoding.
- 45c357e0e85d 17.6 cited
Keep WAL segments by the flushed value of the slot's restart LSN
- 2090edc6f32f 17.6 cited
Keep WAL segments by slot's last saved restart LSN
- ca307d5cec90 18.0 cited

Hi Amit,
Thank you for your reply. Following your suggestion, I have started a new discussion thread for this issue:
https://www.postgresql.org/message-id/f492465f-657e-49af-8317-987460cb68b0.mengjuan.cmj%40alibaba-inc.com <https://www.postgresql.org/message-id/f492465f-657e-49af-8317-987460cb68b0.mengjuan.cmj%40alibaba-inc.com >
Best regards,
suyu.cmj