lc_collate mess

From: Susanne & Udo Krause <su(dot)krause(at)bluewin(dot)ch>
To: pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: lc_collate mess
Date: 2020-11-22 13:31:25
Message-ID: 9120334a-61f8-b801-cbc2-0ccc92282973@bluewin.ch
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Hi there,

the new PostgreSQL has been created from scratch by standard
installation with German_Switzerland, then it does not know:

------------------------------------------------------------------------

C:\Users\postgres\Documents>pg_upgrade.exe --old-datadir "C:/Program
Files/PostgreSQL/12/data" --new-datadir "C:/Program
Files/PostgreSQL/13/data" --old-bindir "C:/Program
Files/PostgreSQL/12/bin" --new-bindir "C:/Program
Files/PostgreSQL/13/bin" --check
Führe Konsistenzprüfungen durch
-------------------------------
Checking cluster versions                                   ok
Checking database user is the install user                  ok
Checking database connection settings                       ok
Checking for prepared transactions                          ok
Checking for reg* data types in user tables                 ok
Checking for contrib/isn with bigint-passing mismatch       ok

lc_collate-Werte für Datenbank »postgres« stimmen nicht überein: alt
»German_Switzerland.1252«, neu »German_Germany.1252«
Fehlgeschlagen, Programm wird beendet

C:\Users\postgres\Documents>

------------------------------------------------------------------------

where is a hint how to fix that? New PostgreSQL did not yet start up, of
course.

Previous migration vom PostgreSQL 9 to PostgreSQL 12 was a messy
nightmare, still not okay.

Thanks in advance

Udo.

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Susanne & Udo Krause 2020-11-22 14:37:03 probably reason of failure - not visible of false positive
Previous Message Zsolt Ero 2020-11-22 11:50:14 Re: BUG #16732: pg_dump creates broken backups