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 efaa44f0-fe56-4fdd-be68-f0272e896af9@app.fastmail.com
Whole thread Raw
In response to Re: Does a cancelled REINDEX CONCURRENTLY need to be messy?  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Does a cancelled REINDEX CONCURRENTLY need to be messy?
List pgsql-hackers
ALTER TABLE DETACH CONCURRENTLY had to deal with this also, and it did it by having a COMPLETE option you can run later in case things got stuck the first time around. I suppose we could do something similar, where the server automatically does the needful, whatever that is.

pgsql-hackers by date:

Previous
From: "Tristan Partin"
Date:
Subject: Re: Meson build updates
Next
From: "Jonathan S. Katz"
Date:
Subject: plan_create_index_workers doesn't account for TOAST