Horton

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

Simon Riggs <simon@2ndquadrant.com>

View thread View on postgr.es
From: Simon Riggs <simon@2ndquadrant.com>
To: Dilip Kumar <dilipbalaut@gmail.com>
Cc: Keisuke Kuroda <keisuke.kuroda.3862@gmail.com>, Amit Kapila <amit.kapila16@gmail.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2020-10-08T09:03:53Z
Lists: pgsql-hackers 
On Thu, 8 Oct 2020 at 09:47, Dilip Kumar <dilipbalaut@gmail.com> wrote:

> > This script will wait 10 seconds after INSERT exits
> > before executing TRUNCATE, please wait for it to run.

Has this been tested with anything other than the one test case?

It would be good to know how the patch handles a transaction that
contains many aborted subtransactions that contain invals.

-- 
Simon Riggs                http://www.enterprisedb.com/

Commits

  1. Execute invalidation messages for each XLOG_XACT_INVALIDATIONS message

  2. WAL Log invalidations at command end with wal_level=logical.