Paul Foerster wrote: > >> 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.
It's hard to imagine that the change of collation is related to the failure to create that constraint. When a value is present in the target table but the FK check does not find it, often the cause is index corruption. But if you've just imported that dump, the index on the target column should be brand new. Still, you may check it with pg_amcheck [1] or try rebuilding it just in case. [1] https://www.postgresql.org/docs/current/app-pgamcheck.html Best regards, -- Daniel Vérité https://postgresql.verite.pro/
