Remove read-only server settings lc_collate and lc_ctype
authorPeter Eisentraut <peter@eisentraut.org>
Wed, 7 Jun 2023 14:57:06 +0000 (16:57 +0200)
committerPeter Eisentraut <peter@eisentraut.org>
Wed, 7 Jun 2023 14:57:06 +0000 (16:57 +0200)
commitb0f6c437160db640d4ea3e49398ebc3ba39d1982
tree7f20cb41b997c06a0f5748415e3185c349941937
parentd64e6468f489effec356ce3501c0f226ac1cfcc0
Remove read-only server settings lc_collate and lc_ctype

The GUC settings lc_collate and lc_ctype are from a time when those
locale settings were cluster-global.  When those locale settings were
made per-database (PG 8.4), the settings were kept as read-only.  As
of PG 15, you can use ICU as the per-database locale provider, so
examining these settings is already less meaningful and possibly
confusing, since you need to look into pg_database to find out what is
really happening, and they would likely become fully obsolete in the
future anyway.

Reviewed-by: Jeff Davis <pgsql@j-davis.com>
Discussion: https://www.postgresql.org/message-id/696054d1-bc88-b6ab-129a-18b8bce6a6f0@enterprisedb.com
12 files changed:
contrib/citext/expected/citext_utf8.out
contrib/citext/expected/citext_utf8_1.out
contrib/citext/sql/citext_utf8.sql
doc/src/sgml/config.sgml
src/backend/utils/init/postinit.c
src/backend/utils/misc/guc_tables.c
src/test/regress/expected/collate.icu.utf8.out
src/test/regress/expected/collate.linux.utf8.out
src/test/regress/expected/collate.windows.win1252.out
src/test/regress/sql/collate.icu.utf8.sql
src/test/regress/sql/collate.linux.utf8.sql
src/test/regress/sql/collate.windows.win1252.sql