| From: | Moshe Jacobson <moshe(at)neadwerx(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: pg_dump dumps EVENT TRIGGER owned by extension |
| Date: | 2013-12-30 19:22:14 |
| Message-ID: | CAJ4CxLnVKJNJyTib05q-jpJ==BdSrLb=0oKzexyD-B_TQdrb=Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Mon, Dec 30, 2013 at 2:02 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> there seem to be two distinct bugs: CREATE EVENT TRIGGER forgets
> to mark the event trigger as a member of its extension, and pg_dump
> doesn't pay any attention anyway when deciding whether to dump the event
> trigger. I've committed fixes for these, but if you have an existing
> extension that should have an event trigger as member, you'll need to use
> ALTER EXTENSION ADD EVENT TRIGGER to clean up the mess.
>
Thank you, Tom.
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 | Janek Sendrowski | 2013-12-30 20:07:16 | Re: bulk insert unique contraint |
| Previous Message | Tom Lane | 2013-12-30 19:02:44 | Re: pg_dump dumps EVENT TRIGGER owned by extension |