Re: Corruption with IMMUTABLE functions in index expression.

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: Corruption with IMMUTABLE functions in index expression.
Дата
Msg-id 477319.1633978762@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Re: Corruption with IMMUTABLE functions in index expression.  (Andres Freund <andres@anarazel.de>)
Ответы Re: Corruption with IMMUTABLE functions in index expression.  (Andres Freund <andres@anarazel.de>)
Список pgsql-hackers
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



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

Предыдущее
От: Peter Geoghegan
Дата:
Сообщение: Re: BUG #17212: pg_amcheck fails on checking temporary relations
Следующее
От: Bharath Rupireddy
Дата:
Сообщение: Accommodate startup process in a separate ProcState array slot instead of in MaxBackends slots.