Re: pg_recvlogical: Prevent flushed data from being re-sent after restarting replication

From: Mircea Cadariu <cadariu(dot)mircea(at)gmail(dot)com>
To: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: pg_recvlogical: Prevent flushed data from being re-sent after restarting replication
Date: 2025-12-03 08:59:18
Message-ID: 67f24571-aad7-4938-8a9a-db8c2317d6ec@gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

On 28/11/2025 02:15, Fujii Masao wrote:
> I've made a few minor adjustments to the test patch.
> The updated version is attached.

Thanks for the updated patch! Nice improvements.

Two futher proposals for the current version of the test.

Shall we use slurp_file then everywhere we need file reads? (instead of
pg_read_file)

The following can be seen as nits for your consideration.

We can consider making the string provided in the "or die" to be
consistent with the comment. We can pick one of the options below and
specify the same for each.

* receive and write the first INSERT / receive first INSERT

* establish a new connection / to reconnect

* receive and write  / receive

If we are mentioning multiple INSERTs instead of just one, might read
better if we add the "s" at the end. This might be just my preference
though, I leave it up to you.

--
Thanks,
Mircea Cadariu

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Heikki Linnakangas 2025-12-03 09:38:02 Re: Using MyDatabaseId in SET_LOCKTAG_APPLY_TRANSACTION
Previous Message Adam Lee 2025-12-03 08:45:32 [PATCH] Make ReScanForeignScan callback optional for FDWs