RE: Newly created replication slot may be invalidated by checkpoint

From: "Hayato Kuroda (Fujitsu)" <kuroda(dot)hayato(at)fujitsu(dot)com>
To: "Zhijie Hou (Fujitsu)" <houzj(dot)fnst(at)fujitsu(dot)com>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
Cc: vignesh C <vignesh21(at)gmail(dot)com>, Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>, Vitaly Davydov <v(dot)davydov(at)postgrespro(dot)ru>, "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org>, suyu(dot)cmj <mengjuan(dot)cmj(at)alibaba-inc(dot)com>, tomas <tomas(at)vondra(dot)me>, michael <michael(at)paquier(dot)xyz>, bharath(dot)rupireddyforpostgres <bharath(dot)rupireddyforpostgres(at)gmail(dot)com>, Alexander Korotkov <aekorotkov(at)gmail(dot)com>
Subject: RE: Newly created replication slot may be invalidated by checkpoint
Date: 2026-01-26 05:35:37
Message-ID: TY7PR01MB14554C9C81D84F9D25B1D7F51F593A@TY7PR01MB14554.jpnprd01.prod.outlook.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Dear Hou,

Thanks for updating the patch. I ran tests and reproducer [1] for all versions.
Confirmed the issue happened before the patch and fixed after applying them.

One difference between master and others is that pg_sync_replication_slots()
on HEAD is not returned. Because the behavior was changed by 0d2d4a0, not
related with the fix.

I feel these patches are enough good shape.

[1]: https://www.postgresql.org/message-id/TY7PR01MB14554DBE84290130EB421DD28F596A%40TY7PR01MB14554.jpnprd01.prod.outlook.com

Best regards,
Hayato Kuroda
FUJITSU LIMITED

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message David G. Johnston 2026-01-26 05:38:16 Re: docs: clarify ALTER TABLE behavior on partitioned tables
Previous Message vaibhave postgres 2026-01-26 05:23:19 docs: warn about post-data-only schema dumps with parallel restore.