Re: BUG #18498: Locking a table from a trigger (with using two sessions) causes a deadlock: the bug or the feature?

From:	Dmitry Koval <d(dot)koval(at)postgrespro(dot)ru>
To:	pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject:	Re: BUG #18498: Locking a table from a trigger (with using two sessions) causes a deadlock: the bug or the feature?
Date:	2024-06-07 08:47:02
Message-ID:	3a6d9e93-3c29-4fc4-b41d-edec72937db9@postgrespro.ru
Views:	Raw Message | Whole Thread | Download mbox | Resend email
Thread:	2024-06-07 07:55:29 from PG Bug reporting form <noreply(at)postgresql(dot)org>  2024-06-07 08:47:02 from Dmitry Koval <d(dot)koval(at)postgrespro(dot)ru> 📎  2024-06-07 08:58:43 from David Rowley <dgrowleyml(at)gmail(dot)com>   2024-06-07 09:02:47 from David Rowley <dgrowleyml(at)gmail(dot)com>    2024-06-07 09:45:26 from Dmitry Koval <d(dot)koval(at)postgrespro(dot)ru>  2024-06-07 17:32:46 from "Wetmore, Matthew (CTR)" <Matthew(dot)Wetmore(at)evernorth(dot)com>
Lists:	pgsql-bugs

Attachment	Content-Type	Size
v1-0001-LOCK-TABLE-with-deadlocks.patch	text/plain	2.3 KB
v1-0001-LOCK-TABLE-wo-errors.patch	text/plain	2.2 KB

In response to

• BUG #18498: Locking a table from a trigger (with using two sessions) causes a deadlock: the bug or the feature? at 2024-06-07 07:55:29 from PG Bug reporting form

Browse pgsql-bugs by date

	From	Date	Subject
Next Message	David Rowley	2024-06-07 08:58:43	Re: BUG #18498: Locking a table from a trigger (with using two sessions) causes a deadlock: the bug or the feature?
Previous Message	PG Bug reporting form	2024-06-07 07:55:29	BUG #18498: Locking a table from a trigger (with using two sessions) causes a deadlock: the bug or the feature?