RE: "ERROR: deadlock detected" when replicating TRUNCATE - Mailing list pgsql-hackers

From tanghy.fnst@fujitsu.com
Subject RE: "ERROR: deadlock detected" when replicating TRUNCATE
Date
Msg-id OS0PR01MB611354A48D0AE47E708D6BB5FB2D9@OS0PR01MB6113.jpnprd01.prod.outlook.com
Whole thread Raw
In response to Re: "ERROR: deadlock detected" when replicating TRUNCATE  (Amit Kapila <amit.kapila16@gmail.com>)
List pgsql-hackers
On Monday, May 17, 2021 5:47 PM, Amit Kapila <amit.kapila16@gmail.com> wrote
> +$node_publisher->safe_psql('postgres',
> + "ALTER SYSTEM SET synchronous_standby_names TO 'any 2(sub5_1,
> sub5_2)'");
> +$node_publisher->safe_psql('postgres', "SELECT pg_reload_conf()");
> 
> Do you really need these steps to reproduce the problem? IIUC, this
> has nothing to do with synchronous replication.

Agreed. 
I tested in asynchronous mode, and could reproduce this problem, too.

The attached patch removed the steps for setting synchronous replication.
And the test passed after applying Peter's patch.
Please take it as your reference.

Regards
Tang


Attachment

pgsql-hackers by date:

Previous
From: Dilip Kumar
Date:
Subject: Re: "ERROR: deadlock detected" when replicating TRUNCATE
Next
From: Amit Kapila
Date:
Subject: Re: Forget close an open relation in ReorderBufferProcessTXN()