Обсуждение: Restore Windows dump to Linux (locale issue)

On 11/23/25 13:41, Ertan Küçükoglu wrote:
> Hello,
> 
> I am using PostgreSQL 18.1 on a Windows system.
> I need to move that database to a Linux system of the same version number.
> 
> Windows system use locales name as tr-TR (this is UTF-8 locale)
> Linux system use locale name as tr_TR.UTF-8
> 
> My cluster backup gives error at restore (I think because of that locale 
> naming difference) as below

What was the complete command you gave to do the dump?

> 
> psql:/db.dump:133: ERROR:  invalid LC_COLLATE locale name: "tr-TR"

What objects where the errors on?

> 
> And a bunch of other errors below.
> 
> What can I do to complete this migration?
> 
> Thanks & Regards,
> Ertan


-- 
Adrian Klaver
adrian.klaver@aklaver.com

On 11/23/25 13:41, Ertan Küçükoglu wrote:
> Hello,
> 
> I am using PostgreSQL 18.1 on a Windows system.
> I need to move that database to a Linux system of the same version number.
> 
> Windows system use locales name as tr-TR (this is UTF-8 locale)
> Linux system use locale name as tr_TR.UTF-8
> 
> My cluster backup gives error at restore (I think because of that locale 
> naming difference) as below
> 
> psql:/db.dump:133: ERROR:  invalid LC_COLLATE locale name: "tr-TR"

I should have added to previous post what does, in psql, the below return:

\l <database_name>

> 
> And a bunch of other errors below.
> 
> What can I do to complete this migration?
> 
> Thanks & Regards,
> Ertan


-- 
Adrian Klaver
adrian.klaver@aklaver.com

=?UTF-8?B?RXJ0YW4gS8O8w6fDvGtvZ2x1?= <ertan.kucukoglu@gmail.com> writes:
> I am using PostgreSQL 18.1 on a Windows system.
> I need to move that database to a Linux system of the same version number.
> Windows system use locales name as tr-TR (this is UTF-8 locale)
> Linux system use locale name as tr_TR.UTF-8
> My cluster backup gives error at restore (I think because of that locale
> naming difference) as below
> psql:/db.dump:133: ERROR:  invalid LC_COLLATE locale name: "tr-TR"

Edit the dump so that the databases are created with Linux-compatible
locale names.  You should find lines like

CREATE DATABASE foo WITH TEMPLATE = template0 ENCODING = 'UTF-8' LOCALE_PROVIDER = libc LOCALE = 'tr-TR';

(details will vary depending on PG version) and changing the locale
strings ought to do the trick.

If the dump file is too big for your editor, consider splitting it
into schema-only and data-only dumps.

            regards, tom lane

On 11/25/25 13:06, Ertan Küçükoglu wrote:

> 
> Hello,
> 

I am not understanding the below.

> I manually created a database on the Linux system.
> Took a database backup and restored it on the Linux system.

That is what started this thread, an issue with a backup from a Windows 
machine.

So where did you get a backup that you could restore?

> This way dump does not include any charset.

Pretty sure it does, it just one that your Linux machine understands.

> 
> Thanks & Regards,
> Ertan


-- 
Adrian Klaver
adrian.klaver@aklaver.com

On 11/25/25 14:03, Ertan Küçükoglu wrote:
> Adrian Klaver <adrian.klaver@aklaver.com 
> <mailto:adrian.klaver@aklaver.com>>, 26 Kas 2025 Çar, 00:20 tarihinde 
> şunu yazdı:
> 
>     On 11/25/25 13:06, Ertan Küçükoglu wrote:
> 
>      >
>      > Hello,
>      >
> 
>     I am not understanding the below.
> 
>      > I manually created a database on the Linux system.
>      > Took a database backup and restored it on the Linux system.
> 
>     That is what started this thread, an issue with a backup from a Windows
>     machine.
> 
>     So where did you get a backup that you could restore?
> 
> 
> Initially it was a pgdump_all backup. Which includes database creation 
> scripts.
> I used only pg_dump backup. Where I restore in an already created database.

Alright I understand now.

> 
> I called pg_dumpall backup as "cluster backup" . It may be my wrong 
> choice of naming.

It is a dump of the all the databases in the cluster as well as the 
cluster global objects, so the naming is correct. I just did not make 
the connection.


-- 
Adrian Klaver
adrian.klaver@aklaver.com