Re: Invalid indexes should not consume update overhead

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: Invalid indexes should not consume update overhead
Дата
Msg-id 1150.1468717127@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Re: Invalid indexes should not consume update overhead  (Greg Stark <stark@mit.edu>)
Ответы Re: Invalid indexes should not consume update overhead  (Peter Geoghegan <pg@heroku.com>)
Список pgsql-bugs
Greg Stark <stark@mit.edu> writes:
> The real solution imho is to actually clean up failed index builds when a
> build fails. That's what normal transactions do when they abort after all.
> This was always the intention but looked like it was going to be a pain and
> was put off (ie I was lazy). It's probably just several layers of
> PG_TRY/PG_CATCH and closing the failed transactions and opening new ones.

No, that wouldn't fix it if the reason the build failed was a crash.

            regards, tom lane

В списке pgsql-bugs по дате отправления:

Предыдущее
От: Greg Stark
Дата:
Сообщение: Re: Invalid indexes should not consume update overhead
Следующее
От: digoal@126.com
Дата:
Сообщение: BUG #14253: b-tree no index range scan?