Re: Invalid indexes should not consume update overhead - Mailing list pgsql-bugs

From Tom Lane
Subject Re: Invalid indexes should not consume update overhead
Date
Msg-id 1150.1468717127@sss.pgh.pa.us
Whole thread Raw
In response to Re: Invalid indexes should not consume update overhead  (Greg Stark <stark@mit.edu>)
Responses Re: Invalid indexes should not consume update overhead
List 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 by date:

Previous
From: Greg Stark
Date:
Subject: Re: Invalid indexes should not consume update overhead
Next
From: digoal@126.com
Date:
Subject: BUG #14253: b-tree no index range scan?