Re: Does a cancelled REINDEX CONCURRENTLY need to be messy? - Mailing list pgsql-hackers

From Álvaro Herrera
Subject Re: Does a cancelled REINDEX CONCURRENTLY need to be messy?
Date
Msg-id 20230704165957.vcrqqt7vl6ak77p2@alvherre.pgsql
Whole thread Raw
In response to Re: Does a cancelled REINDEX CONCURRENTLY need to be messy?  (Michael Paquier <michael@paquier.xyz>)
List pgsql-hackers
On 2023-Jul-04, Michael Paquier wrote:

> On Mon, Jul 03, 2023 at 07:46:27PM +0200, Alvaro Herrera wrote:

> > Perhaps we could have autovacuum check for it, and do it
> > separately of vacuum proper.)
> 
> Being able to reuse some of the worker/launcher parts from autovacuum
> could make things easier for a bgworker implementation, perhaps?

TBH I don't understand what you are thinking about.

-- 
Álvaro Herrera         PostgreSQL Developer  —  https://www.EnterpriseDB.com/
"I can see support will not be a problem.  10 out of 10."    (Simon Wittber)
      (http://archives.postgresql.org/pgsql-general/2004-12/msg00159.php)



pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: Add more sanity checks around callers of changeDependencyFor()
Next
From: Heikki Linnakangas
Date:
Subject: Re: On /*----- comments