Re: Adding REPACK [concurrently]

From: Antonin Houska <ah(at)cybertec(dot)at>
To: Jim Jones <jim(dot)jones(at)uni-muenster(dot)de>
Cc: Srinath Reddy Sadipiralla <srinath2133(at)gmail(dot)com>, alvherre(at)alvh(dot)no-ip(dot)org, Mihail Nikalayeu <mihailnikalayeu(at)gmail(dot)com>, Pg Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Robert Treat <rob(at)xzilla(dot)net>
Subject: Re: Adding REPACK [concurrently]
Date: 2026-03-24 08:48:57
Message-ID: 13637.1774342137@localhost
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Jim Jones <jim(dot)jones(at)uni-muenster(dot)de> wrote:

> while reviewing another patch I noticed that REPACK is trying to access
> temp tables from other sessions.

Thanks for the report. I agree that there's no reason for REPACK to get
blocked on a lock of a table that it will not process anyway. However, as both
VACUUM FULL and CLUSTER in PG 18 appear to have the same problem, I'm not sure
your patch needs to be incorporated in the new feature. Adding a bug fix entry
to the CF seems the appropriate action to me.

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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jakub Wartak 2026-03-24 08:53:44 Re: log XLogPrefetch stats at end of recovery
Previous Message Lakshmi N 2026-03-24 08:28:13 Re: log XLogPrefetch stats at end of recovery