Hi,
On Jul 8, 2018, at 2:19 PM, Alvaro Herrera 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_droppe
On Sun, Jul 08, 2018 at 09:51:47AM -0400, Matt Dee wrote:
> In the documentation for START_REPLICATION, a required argument is the WAL
> location to begin streaming at, and I'm not sure what to use here. I have
> been using 0, and it seems to work fine. Additionally, it seems that when
> --startp
> you can use overloading to define
> several functions of the same name, and just write out one for each
> range type you actually need this functionality for.
Thanks! I was hoping to avoid that, but it's what I wound up doing
after all, as you can see here:
https://github.com/pjungwir/range_agg
On 2018-Jul-08, Demitri Muna wrote:
Hi
> I’ve created a trigger where I want to capture schema-changing events.
> I’m finding that DROP events are not being triggered when using
> “ddl_command_end". The test case below demonstrates this. I am running
> PostgreSQL 10.4. The trigger is fired for th
Hi,
I’ve created a trigger where I want to capture schema-changing events. I’m
finding that DROP events are not being triggered when using “ddl_command_end".
The test case below demonstrates this. I am running PostgreSQL 10.4. The
trigger is fired for the CREATE event, but not DROP TYPE or DROP
Hi,
I am trying to use the streaming replication protocol described in
https://www.postgresql.org/docs/10/static/protocol-replication.html to read
logical decoding events from a replication slot.
I'm doing this by starting replication with START_REPLICATION, and sending
down the most recent posit
