Re: Call EndCopyFrom() after initial table sync in logical replication

From: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
To: cca5507 <cca5507(at)qq(dot)com>
Cc: Shinya Kato <shinya11(dot)kato(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Call EndCopyFrom() after initial table sync in logical replication
Date: 2026-05-08 04:21:31
Message-ID: CAHGQGwHfdbfRRVdQjYRZmT94UMqE1W4MENiaseVtsHWmzkWxBQ@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, May 8, 2026 at 11:34 AM cca5507 <cca5507(at)qq(dot)com> wrote:
>
> Hi,
>
> Maybe we want to add "free_parsestate(pstate);" after the "EndCopyFrom()" as well?

What actual issue could occur if free_parsestate() is not called there?

Since pstate->p_target_relation does not seem to be used afterward,
omitting free_parsestate() appears mostly harmless to me. Bascailly
calling free_parsestate() after make_parsestate() seems intuitive,
but from a quick grep I found several places that call make_parsestate()
without a corresponding free_parsestate().

Regards,

--
Fujii Masao

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Chao Li 2026-05-08 04:21:53 Fix REPACK with WITHOUT OVERLAPS replica identity indexes
Previous Message John Naylor 2026-05-08 03:48:55 Re: Broken build on macOS (Universal / Intel): cpuid instruction not available