RE: "ERROR: deadlock detected" when replicating TRUNCATE

From: "tanghy(dot)fnst(at)fujitsu(dot)com" <tanghy(dot)fnst(at)fujitsu(dot)com>
To: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Peter Smith <smithpb2250(at)gmail(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: RE: "ERROR: deadlock detected" when replicating TRUNCATE
Date: 2021-05-17 09:36:33
Message-ID: OS0PR01MB611354A48D0AE47E708D6BB5FB2D9@OS0PR01MB6113.jpnprd01.prod.outlook.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Monday, May 17, 2021 5:47 PM, Amit Kapila <amit(dot)kapila16(at)gmail(dot)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 Content-Type Size
v3_test_for_deadlock.patch application/octet-stream 2.6 KB

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Kapila 2021-05-17 09:44:33 Re: Forget close an open relation in ReorderBufferProcessTXN()
Previous Message Dilip Kumar 2021-05-17 09:34:40 Re: "ERROR: deadlock detected" when replicating TRUNCATE