Re: Wanted: ALTER TRIGGER ... OWNED BY EXTENSION
| От | Moshe Jacobson |
|---|---|
| Тема | Re: Wanted: ALTER TRIGGER ... OWNED BY EXTENSION |
| Дата | |
| Msg-id | CAJ4CxLk+zncrW0h89c11PAyrQBkvj+mDPhXcDh9Zaoq4k88b0g@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: Wanted: ALTER TRIGGER ... OWNED BY EXTENSION (Moshe Jacobson <moshe@neadwerx.com>) |
| Ответы |
Re: Wanted: ALTER TRIGGER ... OWNED BY EXTENSION
|
| Список | pgsql-general |
On Mon, Mar 31, 2014 at 4:32 PM, Moshe Jacobson <moshe@neadwerx.com> wrote:
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.
I've added the requisite rows to pg_depend, and I know it was correct because \dx+ cyanaudit (my extension) now shows all of the triggers.
However, pg_dump still dumps them, and pg_restore still restores them, causing the same errors as I had before.
Moshe Jacobson
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
"Quality is not an act, it is a habit." -- Aristotle
В списке pgsql-general по дате отправления: