From: Olleg Samoylov <splarv@ya.ru>
To: pgsql-admin@lists.postgresql.org
Subject: A trigger in an extension
Date: Thu, 20 Feb 2025 22:23:18 +0300
Message-ID: <40129c90-138c-4331-a3d6-c04158cb91e0@ya.ru> (raw)
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: splarv@ya.ru, pgsql-admin@lists.postgresql.org
Subject: Re: A trigger in an extension
In-Reply-To: <40129c90-138c-4331-a3d6-c04158cb91e0@ya.ru>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox