aboutsummaryrefslogtreecommitdiff
path: root/src/backend/tcop/postgres.c
diff options
context:
space:
mode:
authorPeter Eisentraut <peter@eisentraut.org>2022-09-13 14:18:45 +0200
committerPeter Eisentraut <peter@eisentraut.org>2022-09-13 14:28:10 +0200
commitda5d4ea5aaac4fc02f2e2aec272efe438dd4e171 (patch)
tree64fdd865cd110f9498114801cac3cf5f9a893b59 /src/backend/tcop/postgres.c
parent8e7a0b4a36741934d1350de5646efd2f3a10951e (diff)
downloadpostgresql-da5d4ea5aaac4fc02f2e2aec272efe438dd4e171.tar.gz
postgresql-da5d4ea5aaac4fc02f2e2aec272efe438dd4e171.zip
Make locale option behavior more consistent
Locale options can be specified for initdb, createdb, and CREATE DATABASE. In initdb, it has always been possible to specify --locale and then some --lc-* option to override a category. CREATE DATABASE and createdb didn't allow that, requiring either the all-categories option or only per-category options. In f2553d43060edb210b36c63187d52a632448e1d2, this was changed in CREATE DATABASE (perhaps by accident?) to be more like the initdb behavior, but createdb still had the old behavior. Now we change createdb to match the behavior of CREATE DATABASE and initdb, and also update the documentation of CREATE DATABASE to match the new behavior, which was not done in the above commit. Author: Marina Polyakova <m.polyakova@postgrespro.ru> Reviewed-by: Justin Pryzby <pryzby@telsasoft.com> Discussion: https://www.postgresql.org/message-id/7c99c132dc9c0ac630e0127f032ac480@postgrespro.ru
Diffstat (limited to 'src/backend/tcop/postgres.c')
0 files changed, 0 insertions, 0 deletions