There was no reason I needed to run full statements in this case. I just
didn't know I could get the type ids like that.
Thanks for all of your help Andres!
On Tue, Feb 10, 2015 at 1:23 PM, Andres Freund
wrote:
> On 2015-02-10 10:33:41 -0800, Xavier Stevens wrote:
> > Sorry to raise the issue
On 2015-02-10 10:33:41 -0800, Xavier Stevens wrote:
> Sorry to raise the issue on startup_cb. I added a whole bunch of logging
> statements and I was only running the section of code I wanted when the
> startup callback had options.
Heh.
Just to make sure: You can pass options via replication pro
Sorry to raise the issue on startup_cb. I added a whole bunch of logging
statements and I was only running the section of code I wanted when the
startup callback had options.
This now gets me to the next issue I encounter. In my output plugin, I'm
trying to use the SPI interface to query about Pos
On Tue, Feb 10, 2015 at 5:59 PM, Andres Freund
wrote:
> On 2015-02-10 11:01:08 +0900, Michael Paquier wrote:
>> Just in case, I have just done a quick test with pg_recvlogical on
>> latest HEAD of REL9_4_STABLE and the startup_cb gets called:
>> DEBUG: received replication command: IDENTIFY_SYSTE
On 2015-02-10 11:01:08 +0900, Michael Paquier wrote:
> Just in case, I have just done a quick test with pg_recvlogical on
> latest HEAD of REL9_4_STABLE and the startup_cb gets called:
> DEBUG: received replication command: IDENTIFY_SYSTEM
> DEBUG: received replication command: START_REPLICATION
Hi,
On 2015-02-09 16:52:59 -0800, Xavier Stevens wrote:
> I'm trying to write a logical decoding plugin and I'm seeing some
> interesting behavior around the startup callback. When I use psql and the
> built-in SQL functions (like pg_logical_slot_peek_changes) to use my module
> I see the startup_
On Tue, Feb 10, 2015 at 9:52 AM, Xavier Stevens wrote:
> I'm trying to write a logical decoding plugin and I'm seeing some
> interesting behavior around the startup callback. When I use psql and the
> built-in SQL functions (like pg_logical_slot_peek_changes) to use my module
> I see the startup_cb
I'm trying to write a logical decoding plugin and I'm seeing some
interesting behavior around the startup callback. When I use psql and the
built-in SQL functions (like pg_logical_slot_peek_changes) to use my module
I see the startup_cb get called. I have written my own streaming
replication client
