Re: Invalid indexes should not consume update overhead

Поиск
Список
Период
Сортировка
От Peter Geoghegan
Тема Re: Invalid indexes should not consume update overhead
Дата
Msg-id CAM3SWZRHPmTZjrvciY+u6NLJfLV=fiWbgVHbdzpVxA7=gfVVyw@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Invalid indexes should not consume update overhead  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-bugs
On Sat, Jul 16, 2016 at 5:58 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> 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.

Could we just have crash recovery perform clean-up to cover that case?


--
Peter Geoghegan

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

Предыдущее
От: digoal@126.com
Дата:
Сообщение: BUG #14253: b-tree no index range scan?
Следующее
От: Amit Kapila
Дата:
Сообщение: Re: BUG #14150: Attempted to delete invisible tuple