Message-ID: <40129c90-138c-4331-a3d6-c04158cb91e0@ya.ru>
Date: Thu, 20 Feb 2025 22:23:18 +0300
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
To: pgsql-admin@lists.postgresql.org
Content-Language: ru, en-US
From: Olleg Samoylov <splarv@ya.ru>
Subject: A trigger in an extension
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: 
 <https://www.postgresql.org/message-id/40129c90-138c-4331-a3d6-c04158cb91e0%40ya.ru>
Precedence: bulk

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