Re: Add CREATE DATABASE LOCALE option - Mailing list pgsql-hackers

From Fabrízio de Royes Mello
Subject Re: Add CREATE DATABASE LOCALE option
Date
Msg-id CAFcNs+pd2+u54zZc08=9Eo8=JxKcaA+JVOJZNSojcsA0LyJQUw@mail.gmail.com
Whole thread Raw
In response to Re: Add CREATE DATABASE LOCALE option  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
Responses Re: Add CREATE DATABASE LOCALE option
List pgsql-hackers

On Thu, Jun 6, 2019 at 6:38 AM Peter Eisentraut <peter.eisentraut@2ndquadrant.com> wrote:
>
> On 2019-06-05 22:31, Fabrízio de Royes Mello wrote:
> > On Wed, Jun 5, 2019 at 5:17 PM Peter Eisentraut
> > <peter.eisentraut@2ndquadrant.com
> > <mailto:peter.eisentraut@2ndquadrant.com>> wrote:
> >>
> >> I propose this patch to add a LOCALE option to CREATE DATABASE.  This
> >> sets both LC_COLLATE and LC_CTYPE with one option.  Similar behavior is
> >> already supported in initdb, CREATE COLLATION, and createdb.
> >>
> >> With collation providers other than libc, having separate lc_collate and
> >> lc_ctype settings is not necessarily applicable, so this is also
> >> preparation for such future functionality.
> >
> > Cool... would be nice also add some test cases.
>
> Right.  Any suggestions where to put them?
>

Hmm... good question... I thought we already have some regression tests for {CREATE|DROP} DATABASE but actually we don't... should we add a new one?

Att,

--
   Fabrízio de Royes Mello         Timbira - http://www.timbira.com.br/
   PostgreSQL: Consultoria, Desenvolvimento, Suporte 24x7 e Treinamento

pgsql-hackers by date:

Previous
From: David Rowley
Date:
Subject: Re: Should we warn against using too many partitions?
Next
From: Andres Freund
Date:
Subject: Re: Sort support for macaddr8