locale - Search results
Mailing lists >> pgsql-bugs >> Thread
2025-04-22 14:39:35 | Re: PostgreSQL v15.12 fails to perform PG_UPGRADE from v13 and v9 on Windows (Avi Uziel)
locale en-US" using Windows installer 15.12. So it is supported, just not supporting the "locale
Mailing lists >> pgsql-bugs >> Thread
2025-04-22 14:30:24 | Re: PostgreSQL v15.12 fails to perform PG_UPGRADE from v13 and v9 on Windows (Manika Singhal)
locale` option is not yet supported by the Windows installers. As an alternative, you can download
Mailing lists >> pgsql-bugs >> Thread
2025-04-22 13:58:06 | Re: PostgreSQL v15.12 fails to perform PG_UPGRADE from v13 and v9 on Windows (Avi Uziel)
locale using the "--locale" flag. This way, the "old" and "new" clusters will have the same
Mailing lists >> pgsql-bugs >> Thread
2025-04-17 22:31:02 | Re: PostgreSQL v15.12 fails to perform PG_UPGRADE from v13 and v9 on Windows (Nico Williams)
wrote: And declare that PG 19 or 20 will not support non-UTF-8 locales / codepages.
Mailing lists >> pgsql-bugs >> Thread
2025-04-17 22:18:10 | Re: PostgreSQL v15.12 fails to perform PG_UPGRADE from v13 and v9 on Windows (Nico Williams)
locales and/or codepages only, and provide a migration tool for existing DBs while not breaking
Mailing lists >> pgsql-bugs >> Thread
2025-04-16 00:11:02 | Re: PostgreSQL v15.12 fails to perform PG_UPGRADE from v13 and v9 on Windows (Thomas Munro)
locale names over its ancient ones in our tooling. We merely pass the strings around
Mailing lists >> pgsql-bugs >> Thread
2025-04-15 19:10:31 | Re: PostgreSQL v15.12 fails to perform PG_UPGRADE from v13 and v9 on Windows (Nico Williams)
locale names. A locale name definitely needs a way to identify a language, so BCP-47 can be part
Mailing lists >> pgsql-bugs >> Thread
2025-04-15 17:51:41 | Re: PostgreSQL v15.12 fails to perform PG_UPGRADE from v13 and v9 on Windows (Manika Singhal)
locales list in either of the following formats during installation: - *BCP-47 names* - *Legacy long
Mailing lists >> pgsql-bugs >> Thread
2025-04-10 10:02:58 | Re: PostgreSQL v15.12 fails to perform PG_UPGRADE from v13 and v9 on Windows (Manika Singhal)
locales dropdown in the installer to list all the BCP names first, followed by the long
Mailing lists >> pgsql-bugs >> Thread
2025-04-10 02:49:18 | Re: PostgreSQL v15.12 fails to perform PG_UPGRADE from v13 and v9 on Windows (Thomas Munro)
locales are 100% compatible with the Vista locales without any official documentation to point to, that
Mailing lists >> pgsql-bugs >> Thread
2025-04-08 08:50:56 | Re: PostgreSQL v15.12 fails to perform PG_UPGRADE from v13 and v9 on Windows (Laurenz Albe)
locale names as much as possible. The problem with the long locale names is not only
Mailing lists >> pgsql-bugs >> Thread
2025-04-07 17:59:36 | Re: PostgreSQL v15.12 fails to perform PG_UPGRADE from v13 and v9 on Windows (Avi Uziel)
locale (default). The cluster locale will be 'English_United States.1252'. 2. Install a cluster on version
Mailing lists >> pgsql-bugs >> Thread
2025-04-04 15:30:13 | Re: PostgreSQL v15.12 fails to perform PG_UPGRADE from v13 and v9 on Windows (Manika Singhal)
locale to its corresponding BCP-47 [2] code name before passing it on to initdb