| From: | Jeff Davis <pgsql(at)j-davis(dot)com> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | [17] CREATE COLLATION default provider |
| Date: | 2023-06-15 04:47:52 |
| Message-ID: | 92f32dd57c4d11777c885d211655aceb799d6ecd.camel@j-davis.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Currently, CREATE COLLATION always defaults the provider to libc.
The attached patch causes it to default to libc if LC_COLLATE/LC_CTYPE
are specified, otherwise default to the current database default
collation's provider.
That way, the provider choice at initdb time then becomes the default
for "CREATE DATABASE ... TEMPLATE template0", which then becomes the
default provider for "CREATE COLLATION (LOCALE='...')".
--
Jeff Davis
PostgreSQL Contributor Team - AWS
| Attachment | Content-Type | Size |
|---|---|---|
| v11-0001-CREATE-COLLATION-default-provider.patch | text/x-patch | 7.9 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeff Davis | 2023-06-15 04:59:40 | Re: pgsql: Fix search_path to a safe value during maintenance operations. |
| Previous Message | Kyotaro Horiguchi | 2023-06-15 04:40:15 | Re: Add a perl function in Cluster.pm to generate WAL |