Re: Adding REPACK [concurrently] - Mailing list pgsql-hackers

From Mihail Nikalayeu
Subject Re: Adding REPACK [concurrently]
Date
Msg-id CADzfLwVFtjBN6YFWV5ziZkxyq5_JaCapWPostwEwBTzQg=fPng@mail.gmail.com
Whole thread
In response to Re: Adding REPACK [concurrently]  (Andres Freund <andres@anarazel.de>)
List pgsql-hackers
Hi!

On Sun, Apr 12, 2026 at 4:05 PM Andres Freund <andres@anarazel.de> wrote:
> I don't think that's as good.  The problem is that that way you're only
> detecting the deadlocks once they have materialized (i.e. once repack actually
> does the lock upgrade), rather than cancelling when we know that the problem
> starts.  Having sessions pointlessly blocked for many hours is bad.

O, I think I understand you now.
You propose to somehow mark SUEL as "going to become AEL, so, the
deadlock detector should treat it as such".
In that case LOCK TABLE should get some kind of "future deadlock detected".

Yep, that feels much better. I'll try to check that approach tomorrow.

Best regards,
Mikhail.



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: StringInfo fixes, v19 edition. Plus a few oddities
Next
From: Alexandre Felipe
Date:
Subject: Re: SLOPE - Planner optimizations on monotonic expressions.