Re: Conflict detection for update_deleted in logical replication

On Tue, Aug 12, 2025 at 2:06 PM shveta malik <shveta.malik@gmail.com> wrote:
>
> 2)
> postgres=# create subscription sub2  connection 'dbname=postgres
> host=localhost user=shveta port=5433' publication pub2 WITH
> (retain_dead_tuples = false, max_conflict_retention_duration=1000);
> NOTICE:  created replication slot "sub2" on publisher
> CREATE SUBSCRIPTION
>
> Shall we give notice that max_conflict_retention_duration is ignored
> as retain_dead_tuples is false.
>

How about disallowing this combination?

--
With Regards,
Amit Kapila.