Re: Logical replication CPU-bound with TRUNCATE/DROP/CREATE many tables

From: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
To: Keisuke Kuroda <keisuke(dot)kuroda(dot)3862(at)gmail(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Logical replication CPU-bound with TRUNCATE/DROP/CREATE many tables
Date: 2020-09-28 02:46:16
Message-ID: CAA4eK1KU17W=s9=P0VR23LHx2jr4vwtryj1A1jKuowcN8xTz4g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Sep 28, 2020 at 7:50 AM Keisuke Kuroda
<keisuke(dot)kuroda(dot)3862(at)gmail(dot)com> wrote:
>
> Hi Amit,
>
> Thank you for the reply!
>
> > However, after commit c55040ccd0 (When wal_level=logical,
> > write invalidations at command end into WAL so that decoding can use
> > this information.) we actually know exactly when we need to execute
> > each invalidation.
>
> I see, thank you for your explaination.
> I'll try to think about the solution by using XLOG_INVALIDATIONS
>

You need to refer to XLOG_XACT_INVALIDATIONS, not XLOG_INVALIDATIONS.

> and referring to the thread
> "PATCH: logical_work_mem and logical streaming of large in-progress
> transactions".
>

Okay. Feel free to clarify your questions if you have any? Are you
interested in writing a patch for the same?

--
With Regards,
Amit Kapila.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message David Rowley 2020-09-28 02:47:22 Re: Small improvements to pg_list.h's linitial(), lsecond(), lthird() etc macros
Previous Message Amit Kapila 2020-09-28 02:41:23 Re: New statistics for tuning WAL buffer size