Re: Undetected Deadlock
Michael Harris <harmic@gmail.com>
From: Michael Harris <harmic@gmail.com>
To: Michael Lewis <mlewis@entrata.com>
Cc: pgsql-general@lists.postgresql.org, Alvaro Herrera <alvherre@alvh.no-ip.org>
Date: 2022-01-28T05:27:57Z
Lists: pgsql-general
> but I would expect drop concurrently to resolve your issue with the two processes conflicting I guess you mean ALTER TABLE DETACH PARTITION ... CONCURRENTLY? DROP TABLE does not seem to have a concurrent option. Still that does seem like a good option to try, thanks for drawing it to my attention. Cheers Mike On Thu, 27 Jan 2022 at 14:20, Michael Lewis <mlewis@entrata.com> wrote: > > There may be a bug so perhaps still pursue reproducing the issue, but I would expect drop concurrently to resolve your issue with the two processes conflicting. Also, perhaps trying"insert, on conflict do update" could be more efficient than the copy but obviously there are too many unknowns and variables for either to be a definite winner.
Commits
-
Make timeout.c more robust against missed timer interrupts.
- d37776e451e3 15.0 landed
- 2e211c16612a 14.3 landed
-
Improve timeout.c's handling of repeated timeout set/cancel.
- 09cf1d522676 14.0 cited