pgsql: Make collation-aware system catalog columns use "C" collation.

Поиск
Список
Период
Сортировка
От Tom Lane
Тема pgsql: Make collation-aware system catalog columns use "C" collation.
Дата
Msg-id E1gZJTj-0004pv-WA@gemulon.postgresql.org
обсуждение исходный текст
Список pgsql-committers
Make collation-aware system catalog columns use "C" collation.

Up to now we allowed text columns in system catalogs to use collation
"default", but that isn't really safe because it might mean something
different in template0 than it means in a database cloned from template0.
In particular, this could mean that cloned pg_statistic entries for such
columns weren't entirely valid, possibly leading to bogus planner
estimates, though (probably) not any outright failures.

In the wake of commit 5e0928005, a better solution is available: if we
label such columns with "C" collation, then their pg_statistic entries
will also use that collation and hence will be valid independently of
the database collation.

This also provides a cleaner solution for indexes on such columns than
the hack added by commit 0b28ea79c: the indexes will naturally inherit
"C" collation and don't have to be forced to use text_pattern_ops.

Also, with the planned improvement of type "name" to be collation-aware,
this policy will apply cleanly to both text and name columns.

Because of the pg_statistic angle, we should also apply this policy
to the tables in information_schema.  This patch does that by adjusting
information_schema's textual domain types to specify "C" collation.
That has the user-visible effect that order-sensitive comparisons to
textual information_schema view columns will now use "C" collation
by default.  The SQL standard says that the collation of those view
columns is implementation-defined, so I think this is legal per spec.
At some point this might allow for translation of such comparisons
into indexable conditions on the underlying "name" columns, although
additional work will be needed before that can happen.

Discussion: https://postgr.es/m/19346.1544895309@sss.pgh.pa.us

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/6b0faf723647a851eaaddfed11e14861f8d0f588

Modified Files
--------------
src/backend/access/common/scankey.c        |  8 ++++----
src/backend/bootstrap/bootstrap.c          |  9 +++++++++
src/backend/catalog/genbki.pl              |  8 +++++++-
src/backend/catalog/information_schema.sql |  6 +++---
src/backend/utils/cache/catcache.c         | 13 +++++++------
src/include/catalog/catversion.h           |  2 +-
src/include/catalog/indexing.h             |  6 +++---
src/test/regress/expected/opr_sanity.out   | 21 ++++++++++++++-------
src/test/regress/sql/opr_sanity.sql        | 19 ++++++++++++-------
9 files changed, 60 insertions(+), 32 deletions(-)


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

Предыдущее
От: Tom Lane
Дата:
Сообщение: pgsql: Update sepgsql regression test results for commit ca4103025.
Следующее
От: Tatsuo Ishii
Дата:
Сообщение: pgsql: Doc: fix typo in "Generic File Access Functions" section.