Re: Increased work_mem for "logical replication tablesync worker" only? - Mailing list pgsql-hackers

From Amit Kapila
Subject Re: Increased work_mem for "logical replication tablesync worker" only?
Date
Msg-id CAA4eK1LkpwvOcR6RVNHcEXocA5QK6o3btuwnBHT7-=AZUXPyjA@mail.gmail.com
Whole thread Raw
In response to Re: Increased work_mem for "logical replication tablesync worker" only?  (Dmitry Koterov <dmitry.koterov@gmail.com>)
List pgsql-hackers
On Wed, Feb 5, 2025 at 9:50 AM Dmitry Koterov <dmitry.koterov@gmail.com> wrote:
>
> Only one index, the primary key.
>
> ChatGPT tells that temp files may be used, when bytea columns (or heavily toasted ones) are utilized, but it can’t
explain,why. To me, it’s hard to believe that on the destination, the COPY stream receiver puts almost all of the
receiveddata to temp files, then waits for COPY to finish, and only then moves that temp files to data area, because of
thelarge transaction or something. Would be cool to understand the reason. 
>

One idea is that temporarily you drop the index before copy and see
what happens. Is it possible for you to share a self-contained test
case?

--
With Regards,
Amit Kapila.



pgsql-hackers by date:

Previous
From: Dilip Kumar
Date:
Subject: Re: Conflict detection for update_deleted in logical replication
Next
From: Masahiko Sawada
Date:
Subject: Re: Make COPY format extendable: Extract COPY TO format implementations