Hi all.
Server version is 16.6.
I have the extension pgpro_scheduler. In the exception there are two
tables and the trigger on one of them that write to the other. I was
surprised but when I load dump created by pg_dump this trigger is
created in the pre-data stage (automatically by create extension) early
and thus has wrong behavior when uploaded data in the data stage (lead
to duplication of primary key).
I do workaround by creating superuser with
session_replication_role=replica. But what was wrong? Is this bug inside
pg_dump or pg_restore or extension pgpro_scheduler? Or something other?
--
Olleg
