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

From: "Yilin Zhang" <jiezhilove(at)126(dot)com>
To: "Fujii Masao" <masao(dot)fujii(at)gmail(dot)com>
Cc: "Mircea Cadariu" <cadariu(dot)mircea(at)gmail(dot)com>, "PostgreSQL Hackers" <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re:Re: pg_recvlogical: Prevent flushed data from being re-sent after restarting replication
Date: 2025-12-04 09:40:57
Message-ID: 21f78e1a.858b.19ae8bc7b4f.Coremail.jiezhilove@126.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 28/11/2025 02:15, Fujii Masao <masao(dot)fujii(at)gmail(dot)com> wrote:
> I've made a few minor adjustments to the test patch.
> The updated version is attached.

Hi,
I was reading your code and had a question about the new code you added in the main() function of pg_recvlogical.c:
if (outfd != -1 && strcmp(outfile, "-") != 0)
OutputFsync(feGetCurrentTimestamp());
In the stream loop, the StreamLogicalLog() function already contains similar code:
if (outfd != -1 &&
feTimestampDifferenceExceeds(output_last_fsync, now,
fsync_interval))
{
if (!OutputFsync(now))
goto error;
}

If the outfile becomes unwritable due to external reasons, would the error reporting here be redundant with the error handling in StreamLogicalLog()?

Best regards,
--
Yilin Zhang

In response to

Browse pgsql-hackers by date

  From Date Subject
Previous Message Daniel Gustafsson 2025-12-04 09:34:34 Re: Remove unused function parameters, part 2: replication