Request a Demo
Home   >   mailing lists

Re: Call EndCopyFrom() after initial table sync in logical replication - Mailing list pgsql-hackers

From Fujii Masao
Subject Re: Call EndCopyFrom() after initial table sync in logical replication
Date
Msg-id CAHGQGwEpwuq9U=Hhx3BbfGY-RrJ5rFvdQopO+0xyAuLVsMdfWA@mail.gmail.com
Whole thread
In response to Call EndCopyFrom() after initial table sync in logical replication  (Shinya Kato <shinya11.kato@gmail.com>)
Responses Re: Call EndCopyFrom() after initial table sync in logical replication
List pgsql-hackers
Tree view 
On Mon, May 4, 2026 at 4:58 PM Shinya Kato <shinya11.kato@gmail.com> wrote:
>
> Hi hackers,
>
> While reading the logical replication initial table sync code, I
> noticed that copy_table() calls BeginCopyFrom() and CopyFrom() but
> never calls the matching EndCopyFrom().
>
> EndCopyFrom() calls pgstat_progress_end_command(), which resets
> st_progress_command to PROGRESS_COMMAND_INVALID. Without that call,
> the backend status entry continues to report an active COPY operation
> while the tablesync worker proceeds to WAL catchup. As a result,
> pg_stat_progress_copy shows a stale entry for the entire WAL catchup
> phase.
>
> Attached patch adds EndCopyFrom(cstate) immediately after
> CopyFrom(cstate) returns.

Thanks for the patch! It looks good to me.
Barring any objections, I will commit the patch.

Regards,

--
Fujii Masao

pgsql-hackers by date:

Previous
From: Tobias Bussmann
Date:
Subject: Re: Broken build on macOS (Universal / Intel): cpuid instruction not available
Next
From: Tom Lane
Date:
Subject: Re: Broken build on macOS (Universal / Intel): cpuid instruction not available