<div>Olleg Samoylov <<a href="mailto:splarv(at)ya(dot)ru" rel="noopener noreferrer">splarv(at)ya(dot)ru</a>> writes:</div><blockquote><blockquote> I have the extension pgpro_scheduler. In the exception there are two<br /> tables and the trigger on one of them that write to the other. I was<br /> surprised but when I load dump created by pg_dump this trigger is<br /> created in the pre-data stage (automatically by create extension) early<br /> and thus has wrong behavior when uploaded data in the data stage (lead<br /> to duplication of primary key).</blockquote><p><br />pg_dump does not like to editorialize on the contents of extensions.<br />It just does CREATE EXTENSION and doesn't inquire into what's in<br />them.</p></blockquote><div> </div><div>I saw this.</div><div> </div><blockquote><p>I'd argue that if you need triggers like this, maybe you should rethink your data model.<br /> regards, tom lane</p></blockquote><div> </div><div>This is not my extension. This is foreign extension that emulate sheduler or cron behaviour similar to oracle. Two tables: the second is history table where logged changes of the first cron table.</div><div> </div><div>The question is: is this somehow violate documented rules for extensions, so I can point the extension developers to the documentation? May be triggers is explicitly forbidden for extensions? Or may be need to document this?</div><blockquote> </blockquote>