pgsql: Preserve opclass parameters across REINDEX CONCURRENTLY

Поиск
Список
Период
Сортировка
От Michael Paquier
Тема pgsql: Preserve opclass parameters across REINDEX CONCURRENTLY
Дата
Msg-id E1mhNGI-0003wH-TC@gemulon.postgresql.org
обсуждение исходный текст
Список pgsql-committers
Preserve opclass parameters across REINDEX CONCURRENTLY

The opclass parameter Datums from the old index are fetched in the same
way as for predicates and expressions, by grabbing them directly from
the system catalogs.  They are then copied into the new IndexInfo that
will be used for the creation of the new copy.

This caused the new index to be rebuilt with default parameters rather
than the ones pre-defined by a user.  The only way to get back a new
index with correct opclass parameters would be to recreate a new index
from scratch.

The issue has been introduced by 911e702.

Author: Michael Paquier
Reviewed-by: Zhihong Yu
Discussion: https://postgr.es/m/YX0CG/QpLXcPr8HJ@paquier.xyz
Backpatch-through: 13

Branch
------
REL_14_STABLE

Details
-------
https://git.postgresql.org/pg/commitdiff/f255de9a456531d917a7488ad9d084201dedcfd2

Modified Files
--------------
src/backend/catalog/index.c                | 10 ++++++++++
src/test/regress/expected/create_index.out | 19 +++++++++++++++++++
src/test/regress/sql/create_index.sql      |  9 +++++++++
3 files changed, 38 insertions(+)


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

Предыдущее
От: Tom Lane
Дата:
Сообщение: pgsql: Don't try to read a multi-GB pg_stat_statements file in one call
Следующее
От: Michael Paquier
Дата:
Сообщение: pgsql: Add TAP test for pg_receivewal with timeline switch