From: Tom Lane <tgl@sss.pgh.pa.us>
To: Olleg Samoylov <splarv@ya.ru>
cc: pgsql-admin@lists.postgresql.org
Subject: Re: A trigger in an extension
In-reply-to: <40129c90-138c-4331-a3d6-c04158cb91e0@ya.ru>
References: <40129c90-138c-4331-a3d6-c04158cb91e0@ya.ru>
Comments: In-reply-to Olleg Samoylov <splarv@ya.ru>
	message dated "Thu, 20 Feb 2025 22:23:18 +0300"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <2790098.1740079810.1@sss.pgh.pa.us>
Date: Thu, 20 Feb 2025 14:30:10 -0500
Message-ID: <2790099.1740079810@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/2790099.1740079810%40sss.pgh.pa.us>
Precedence: bulk

Olleg Samoylov <splarv@ya.ru> writes:
> 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).

pg_dump does not like to editorialize on the contents of extensions.
It just does CREATE EXTENSION and doesn't inquire into what's in
them.  I'd argue that if you need triggers like this, maybe you
should rethink your data model.

			regards, tom lane