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

From Antonin Houska
Subject Re: Adding REPACK [concurrently]
Date
Msg-id 13637.1774342137@localhost
Whole thread Raw
In response to Re: Adding REPACK [concurrently]  (Jim Jones <jim.jones@uni-muenster.de>)
Responses Re: Adding REPACK [concurrently]
List pgsql-hackers
Jim Jones <jim.jones@uni-muenster.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



pgsql-hackers by date:

Previous
From: Lakshmi N
Date:
Subject: Re: log XLogPrefetch stats at end of recovery
Next
From: Jakub Wartak
Date:
Subject: Re: log XLogPrefetch stats at end of recovery