Andres Freund <andres@anarazel.de> writes:
> Perhaps we could set pg_index.indisvalid to false initially, and if opening an
> index where pg_index.indisvalid error out with a different error message if
> TransactionIdIsCurrentTransactionId(xmin). And then use an inplace update to
> set indisvalid to true, to avoid the bloat?
I still can't get excited about it ... but yeah, update-in-place would
be enough to remove the bloat objection. I doubt we need any code
changes beyond changing the indisvalid state.
regards, tom lane
