Postgres Pro
Downloads
Home   >   mailing lists

Re: Logical replication CPU-bound with TRUNCATE/DROP/CREATE many tables - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: Logical replication CPU-bound with TRUNCATE/DROP/CREATE many tables
Date
Msg-id CANP8+jJZYksBdEbNBX7J5b8zoGoTDfic0NP0KTh6aVkj+Ft9SA@mail.gmail.com
Whole thread Raw
In response to Re: Logical replication CPU-bound with TRUNCATE/DROP/CREATE many tables  (Dilip Kumar <dilipbalaut@gmail.com>)
Responses Re: Logical replication CPU-bound with TRUNCATE/DROP/CREATE many tables  (Amit Kapila <amit.kapila16@gmail.com>)
List pgsql-hackers
Tree view 
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/

pgsql-hackers by date:

Previous
From: Dilip Kumar
Date:
Subject: Re: Logical replication CPU-bound with TRUNCATE/DROP/CREATE many tables
Next
From: "tsunakawa.takay@fujitsu.com"
Date:
Subject: RE: Transactions involving multiple postgres foreign servers, take 2