| From: | Michael Harris <harmic(at)gmail(dot)com> |
|---|---|
| To: | Michael Lewis <mlewis(at)entrata(dot)com> |
| Cc: | pgsql-general(at)lists(dot)postgresql(dot)org, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
| Subject: | Re: Undetected Deadlock |
| Date: | 2022-01-28 05:27:57 |
| Message-ID: | CADofcAXnXRx0b-Swy2vzAAT-rD-_7MsU0Cxw+vVoHYx8oAuoQg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| 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(at)entrata(dot)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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Umair Shahid | 2022-01-28 11:21:37 | Re: PostgreSQL Management and monitoring tool |
| Previous Message | Merlin Moncure | 2022-01-27 23:10:42 | Re: Counting the number of repeated phrases in a column |