| From: | Demitri Muna <postgresql(at)demitri(dot)com> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: ddl_command_end not firing DROP events |
| Date: | 2018-07-09 04:09:17 |
| Message-ID: | BFA75921-1860-40E1-90AA-34540A712C4B@demitri.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Hi,
On Jul 8, 2018, at 2:19 PM, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> wrote:
> As I recall, handling of DROP events in the ddl_command_end event is not
> completely consistent. You may even find that some DROP events are not
> returned by pg_event_trigger_ddl_commands. I suggest you stick to
> pg_event_trigger_dropped_objects() instead (for which you need
> sql_drop).
That's what I'm seeing as well and have a workaround in place that does just that. But to track schema changes requires two triggers and two functions. Which is fine, it works, but I'm wondering if it's a documentation issue or an outright bug.
Cheers,
Demitri
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Łukasz Jarych | 2018-07-09 09:14:22 | Re: Cloning schemas |
| Previous Message | Michael Paquier | 2018-07-09 01:55:19 | Re: Specifying WAL Location in Streaming Replication |