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-29 12:45:03
Message-ID: 5a551837-50ae-4530-8070-eeed9087ca1f@gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

Thanks for the patch updates.

On 26/12/2025 10:28, Fujii Masao wrote:
> Maybe it's better to use slurp_file(). We already have wait_for_log() to
> wait for a message in the cluster's log file, but there's no helper function
> to wait for specific content to appear in an arbitrary file.
>
> To support waiting for output in pg_recvlogical's output file,
> I added a new helper that uses slurp_file() (see the attached 0002 patch).
> I also updated the 0003 patch (the pg_recvlogical reconnection test) to
> use this helper instead of pg_read_file(). Thoughts?

Agreed, nice addition.

I applied the v3-000* patch set and it builds successfully and passes
the tests on my laptop.

However the CI seems not completely happy yet, with previous 2 runs not
green for Windows. Could it be there's an issue with executing the test
on Windows?

--
Thanks,
Mircea Cadariu

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Kirill Reshke 2025-12-29 12:51:21 Re: GIN pageinspect support for entry tree and posting tree
Previous Message vignesh C 2025-12-29 11:10:46 Re: [Proposal] Adding Log File Capability to pg_createsubscriber