Re: Wanted: ALTER TRIGGER ... OWNED BY EXTENSION - Mailing list pgsql-general

From Moshe Jacobson
Subject Re: Wanted: ALTER TRIGGER ... OWNED BY EXTENSION
Date
Msg-id CAJ4CxLmCPf4B5Z=8rqZygE5tfxKcNbLP5qcvzct1Ex9W7FNomQ@mail.gmail.com
Whole thread Raw
In response to Re: Wanted: ALTER TRIGGER ... OWNED BY EXTENSION  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Wanted: ALTER TRIGGER ... OWNED BY EXTENSION  (Moshe Jacobson <moshe@neadwerx.com>)
List pgsql-general

On Mon, Mar 31, 2014 at 4:20 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
I'm suspicious that the problem is exactly lack of pg_depend records ---
pg_dump/pg_restore relies on those for correct ordering of parallel
operations.  What method are you using to create these triggers (not
the functions, the per-table pg_trigger records)?

There is a trigger function on the extension's config table that creates the trigger functions and installs them (both from the same function). I am about to try playing with pg_depend to see if it has the desired effect.


Moshe Jacobson
Manager of Systems Engineering, Nead Werx Inc.
2323 Cumberland Parkway · Suite 201 · Atlanta, GA 30339

"Quality is not an act, it is a habit." -- Aristotle

pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: Wanted: ALTER TRIGGER ... OWNED BY EXTENSION
Next
From: Si Chen
Date:
Subject: Re: getting the current query from pg_stat_activity