Re: Invalid indexes should not consume update overhead

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Greg Stark <stark(at)mit(dot)edu>
Cc: Tomasz Ostrowski <tometzky+pg(at)ato(dot)waw(dot)pl>, PostgreSQL Bugs <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: Invalid indexes should not consume update overhead
Date: 2016-07-17 00:58:47
Message-ID: 1150.1468717127@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Greg Stark <stark(at)mit(dot)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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message digoal 2016-07-17 03:03:16 BUG #14253: b-tree no index range scan?
Previous Message Greg Stark 2016-07-17 00:09:21 Re: Invalid indexes should not consume update overhead