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

From: Simon Riggs <simon(at)2ndquadrant(dot)com>
To: Dilip Kumar <dilipbalaut(at)gmail(dot)com>
Cc: Keisuke Kuroda <keisuke(dot)kuroda(dot)3862(at)gmail(dot)com>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Logical replication CPU-bound with TRUNCATE/DROP/CREATE many tables
Date: 2020-10-08 09:03:53
Message-ID: CANP8+jJZYksBdEbNBX7J5b8zoGoTDfic0NP0KTh6aVkj+Ft9SA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, 8 Oct 2020 at 09:47, Dilip Kumar <dilipbalaut(at)gmail(dot)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/

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message tsunakawa.takay@fujitsu.com 2020-10-08 09:05:27 RE: Transactions involving multiple postgres foreign servers, take 2
Previous Message Dilip Kumar 2020-10-08 09:02:57 Re: Logical replication CPU-bound with TRUNCATE/DROP/CREATE many tables