From b0f6c437160db640d4ea3e49398ebc3ba39d1982 Mon Sep 17 00:00:00 2001 From: Peter Eisentraut Date: Wed, 7 Jun 2023 16:57:06 +0200 Subject: 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 Discussion: https://www.postgresql.org/message-id/696054d1-bc88-b6ab-129a-18b8bce6a6f0@enterprisedb.com --- doc/src/sgml/config.sgml | 32 -------------------------------- 1 file changed, 32 deletions(-) (limited to 'doc/src') diff --git a/doc/src/sgml/config.sgml b/doc/src/sgml/config.sgml index 5da74b3c406..19c133b02d0 100644 --- a/doc/src/sgml/config.sgml +++ b/doc/src/sgml/config.sgml @@ -10788,38 +10788,6 @@ dynamic_library_path = 'C:\tools\postgresql;H:\my_project\lib;$libdir' - - lc_collate (string) - - lc_collate configuration parameter - - - - - Reports the locale in which sorting of textual data is done. - See for more information. - This value is determined when a database is created. - - - - - - lc_ctype (string) - - lc_ctype configuration parameter - - - - - Reports the locale that determines character classifications. - See for more information. - This value is determined when a database is created. - Ordinarily this will be the same as lc_collate, - but for special applications it might be set differently. - - - - max_function_args (integer) -- cgit v1.2.3