Is there support to use custom LC_COLLATE and LC_CTYPE?

Hi.

Is there support to use custom LC_COLLATE and LC_CTYPE when specifying databases to be created?

It seems the docker image you provide don't support this? I guess you use the PostgreSQL Docker Community library as base for your docker image builds?
E.g this: https://github.com/docker-library/postgres/blob/master/9.6/Dockerfile

I've tried to change the encoding in the manifest like this:

... patroni: initdb: encoding: "UTF8" locale: "nb_NO.UTF8" ....

I managed to build a docker image with support for nb_NO.UTF8 by using the Dockerfile referenced over and adding this:

localedef -i en_US -c -f UTF-8 -A /usr/share/locale/locale.alias en_US.UTF-8; \ localedef -i nb_NO -f UTF-8 nb_NO.UTF-8
But for what I know patroni uses it own docker registry.

So is there a solution for this?

Let me know I should post this issue in the patroni or spilo repo instead of this.

Br,
Lennart

Start with the manifest's initdb.encoding and initdb.locale settings, then compare their handling with the referenced PostgreSQL 9.6 Dockerfile and its locale-generation commands. Done means custom LC_COLLATE and LC_CTYPE values are supported by the provided image, or the image limitation and required setup are clearly documented.