diff options
| author | Peter Eisentraut <peter@eisentraut.org> | 2022-03-17 11:11:21 +0100 |
|---|---|---|
| committer | Peter Eisentraut <peter@eisentraut.org> | 2022-03-17 11:13:16 +0100 |
| commit | f2553d43060edb210b36c63187d52a632448e1d2 (patch) | |
| tree | 7c75fca6ad45c4c25f8b2c6d3d51fa871d2c72d8 /src/backend/executor/nodeModifyTable.c | |
| parent | f6f0db4d62400ff88f523dcc4d7e25f9506bc0d8 (diff) | |
| download | postgresql-f2553d43060edb210b36c63187d52a632448e1d2.tar.gz postgresql-f2553d43060edb210b36c63187d52a632448e1d2.zip | |
Add option to use ICU as global locale provider
This adds the option to use ICU as the default locale provider for
either the whole cluster or a database. New options for initdb,
createdb, and CREATE DATABASE are used to select this.
Since some (legacy) code still uses the libc locale facilities
directly, we still need to set the libc global locale settings even if
ICU is otherwise selected. So pg_database now has three
locale-related fields: the existing datcollate and datctype, which are
always set, and a new daticulocale, which is only set if ICU is
selected. A similar change is made in pg_collation for consistency,
but in that case, only the libc-related fields or the ICU-related
field is set, never both.
Reviewed-by: Julien Rouhaud <rjuju123@gmail.com>
Discussion: https://www.postgresql.org/message-id/flat/5e756dd6-0e91-d778-96fd-b1bcb06c161a%402ndquadrant.com
Diffstat (limited to 'src/backend/executor/nodeModifyTable.c')
0 files changed, 0 insertions, 0 deletions