Re: Index bloat and REINDEX/VACUUM optimization for partial index

Поиск
Список
Период
Сортировка
От Peter Geoghegan
Тема Re: Index bloat and REINDEX/VACUUM optimization for partial index
Дата
Msg-id CAH2-Wz=Szg0BZfuFW=ixj-mQQOSAgCHdS9kv+Lvvxv5M_JLS_A@mail.gmail.com
обсуждение исходный текст
Ответ на Index bloat and REINDEX/VACUUM optimization for partial index  (jayaprabhakar k <jayaprabhakar@gmail.com>)
Ответы Re: Index bloat and REINDEX/VACUUM optimization for partial index  (jayaprabhakar k <jayaprabhakar@gmail.com>)
Список pgsql-performance
Дерево обсуждения 
On Mon, Aug 28, 2023 at 5:33 PM jayaprabhakar k <jayaprabhakar@gmail.com> wrote:
> REINDEX requires a full table scan
>
> Roughly create a new index, rename index, drop old index.
> REINDEX is not incremental. running reindex frequently does not reduce the future reindex time.

You didn't say which Postgres version you're on. Note that Postgres 14
can deal with index bloat a lot better than earlier versions could.
This is known to work well with partial indexes. See:

https://www.postgresql.org/message-id/flat/CAL9smLAjt9mZC2%3DqBeJwuNPq7KMAYGTWWQw_hvA-Lfo0b3ycow%40mail.gmail.com

--
Peter Geoghegan

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

Предыдущее
От: jayaprabhakar k
Дата:
Сообщение: Index bloat and REINDEX/VACUUM optimization for partial index
Следующее
От: Philippe Pepiot
Дата:
Сообщение: Range partitioning query performance with date_trunc (vs timescaledb)