Re: Restore Windows dump to Linux (locale issue)

Brent Wood <Brent.Wood@niwa.co.nz>, 24 Kas 2025 Pzt, 01:42 tarihinde şunu
yazdı:

> If the dump file is too big to edit conventionally, piping it through a
> stream editor like sed to make the required changes works nicely.
> It can be done on the fly in the restore process if required.
>
> Brent Wood
>
> Principal Technician, Fisheries
> NIWA
> DDI:  +64 (4) 3860529
> ------------------------------
> *From:* Tom Lane <tgl@sss.pgh.pa.us>
> *Sent:* Monday, 24 November 2025 11:02
> *To:* Ertan Küçükoglu <ertan.kucukoglu@gmail.com>
> *Cc:* pgsql-general@lists.postgresql.org <
> pgsql-general@lists.postgresql.org>
> *Subject:* Re: Restore Windows dump to Linux (locale issue)
>
> =?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
>

Hello,

I manually created a database on the Linux system.
Took a database backup and restored it on the Linux system.
This way dump does not include any charset.

Thanks & Regards,
Ertan