Re: libc to libicu via pg_dump/pg_restore?
От | Paul Foerster |
---|---|
Тема | Re: libc to libicu via pg_dump/pg_restore? |
Дата | |
Msg-id | D46171D1-80B9-4E81-BC26-D47319B90CE3@gmail.com обсуждение исходный текст |
Ответ на | Re: libc to libicu via pg_dump/pg_restore? (Adrian Klaver <adrian.klaver@aklaver.com>) |
Список | pgsql-general |
Hi Adrian, > On 6 Feb 2025, at 17:31, Adrian Klaver <adrian.klaver@aklaver.com> wrote: > > 1) Log into postgres database and do: > > a) DROP DATABASE mydb; > b) CREATE DATABASE mydb <options>; > > 2) pg_restore -d mydb mydb.dump.gz With create database <options> being "template template0", this is what my script does. But I need the -cC options for pg_restoreto get ACLs back. Leaving out either one of them will not get me the ACLs back. >> pg_restore: error: could not execute query: ERROR: insert or update on table "table_1" violates foreign key constraint"..._fk" >> DETAIL: Key (dokument_id)=(1000033680) is not present in table "...". > > Is dokument_id an integer field? Yes, it's a bigint. > In a follow post you said: > > "Everything works for all databases. Only this one has that problem." > > Do you mean you made the same libc --> icu change on the other databases with no errors? Yes, I have that PostgreSQL 15.10 cluster with locale provider libc with about 40 databases. I initdb'ed a new PostgreSQL17.2 cluster with icu as locale provider and did a "create database ... template template0" for all about 40 databases.Then I did the mentioned pg_restore for each of them as a parallel background job in the shell. The whole database cluster is about 1.2 TB in size so I have to find ways to restore as many databases in parallel as possible.However pg_restore only fails on this single database. All others in that database cluster work fine. Cheers Paul
В списке pgsql-general по дате отправления: