| From: | Moshe Jacobson <moshe(at)neadwerx(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Wanted: ALTER TRIGGER ... OWNED BY EXTENSION |
| Date: | 2014-03-31 20:51:37 |
| Message-ID: | CAJ4CxLk+zncrW0h89c11PAyrQBkvj+mDPhXcDh9Zaoq4k88b0g@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Mon, Mar 31, 2014 at 4:32 PM, Moshe Jacobson <moshe(at)neadwerx(dot)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
Manager of Systems Engineering, Nead Werx Inc. <http://www.neadwerx.com>
2323 Cumberland Parkway · Suite 201 · Atlanta, GA 30339
"Quality is not an act, it is a habit." -- Aristotle
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Scott Marlowe | 2014-03-31 21:05:27 | Re: Why does "checkpointer" is consumig ~1.2Gb of RAM? |
| Previous Message | Edson Richter | 2014-03-31 20:46:42 | Re: Why does "checkpointer" is consumig ~1.2Gb of RAM? |