Re: Does a cancelled REINDEX CONCURRENTLY need to be messy?

Поиск
Список
Период
Сортировка
От Álvaro Herrera
Тема Re: Does a cancelled REINDEX CONCURRENTLY need to be messy?
Дата
Msg-id efaa44f0-fe56-4fdd-be68-f0272e896af9@app.fastmail.com
обсуждение исходный текст
Ответ на Re: Does a cancelled REINDEX CONCURRENTLY need to be messy?  (Tom Lane <tgl@sss.pgh.pa.us>)
Ответы Re: Does a cancelled REINDEX CONCURRENTLY need to be messy?  (Thom Brown <thom@linux.com>)
Список 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 по дате отправления:

Предыдущее
От: "Tristan Partin"
Дата:
Сообщение: Re: Meson build updates
Следующее
От: "Jonathan S. Katz"
Дата:
Сообщение: plan_create_index_workers doesn't account for TOAST