| From: | Jeff Davis <jdavis(at)postgresql(dot)org> |
|---|---|
| To: | pgsql-committers(at)lists(dot)postgresql(dot)org |
| Subject: | pgsql: Fix CREATE DATABASE when template0 has ICU rules. |
| Date: | 2026-11-19 04:04:53 |
| Message-ID: | E1xTtOG-00000000KjJ-2s0E@gemulon.postgresql.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
Fix CREATE DATABASE when template0 has ICU rules.
Most fields, when not specified by the CREATE DATABASE command, are
simply copied from the template. But when the template has ICU rules,
and the new database uses a different provider (which is only possible
with template0), then we should ignore the ICU rules from the
template. But after commit 2d819a08a1, it tried to copy the ICU rules,
and the command resulted in an error.
This commit restores the prior behavior, which ignores the ICU rules
from the template if the new provider is not ICU.
Author: shihao zhong <zhong950419(at)gmail(dot)com>
Reported-by: Heikki Linnakangas <hlinnaka(at)iki(dot)fi>
Discussion: https://postgr.es/m/c97d5993-5d9f-4f75-97f1-7e69643e37c0@iki.fi
Backpatch-through: 17
Branch
------
REL_17_STABLE
Details
-------
https://git.postgresql.org/pg/commitdiff/d8199a61d0e58a91af5088110388215816aad264
Modified Files
--------------
src/backend/commands/dbcommands.c | 2 +-
src/test/icu/t/010_database.pl | 44 +++++++++++++++++++++++++++++++++++++++
2 files changed, 45 insertions(+), 1 deletion(-)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fujii Masao | 2026-11-19 04:30:47 | pgsql: Avoid delaying WAL receiver shutdown while draining WAL |
| Previous Message | Jeff Davis | 2026-11-19 04:04:48 | pgsql: Fix CREATE DATABASE when template0 has ICU rules. |