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

From Antonin Houska
Subject Re: Adding REPACK [concurrently]
Date
Msg-id 112208.1776173876@localhost
Whole thread
In response to Re: Adding REPACK [concurrently]  (Andres Freund <andres@anarazel.de>)
Responses Re: Adding REPACK [concurrently]
List pgsql-hackers
Andres Freund <andres@anarazel.de> wrote:

> On 2026-04-12 15:31:20 +0200, Mihail Nikalayeu wrote:
> > Instead of cancelling the backend entered the deadlock detector - it
> > cancel some another (nearest hard edge) until it is possible to get the
> > lock (either by
> > reordering or directly).
> 
> 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.

This is my hack that tries to do that.

-- 
Antonin Houska
Web: https://www.cybertec-postgresql.com


Attachment

pgsql-hackers by date:

Previous
From: Nazir Bilal Yavuz
Date:
Subject: Re: meson html:alias vs. html:custom
Next
From: Andres Freund
Date:
Subject: Re: Adding REPACK [concurrently]