Re: Logical replication CPU-bound with TRUNCATE/DROP/CREATE many tables
Amit Kapila <amit.kapila16@gmail.com>
From: Amit Kapila <amit.kapila16@gmail.com>
To: Keisuke Kuroda <keisuke.kuroda.3862@gmail.com>
Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2020-09-28T02:46:16Z
Lists: pgsql-hackers
On Mon, Sep 28, 2020 at 7:50 AM Keisuke Kuroda <keisuke.kuroda.3862@gmail.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.
Commits
-
Execute invalidation messages for each XLOG_XACT_INVALIDATIONS message
- d7eb52d7181d 14.0 landed
-
WAL Log invalidations at command end with wal_level=logical.
- c55040ccd017 14.0 cited