Re: Way to access LSN (for each transaction) by directly talking to postgres? - Mailing list pgsql-hackers

From Joshua Bay
Subject Re: Way to access LSN (for each transaction) by directly talking to postgres?
Date
Msg-id CABb-U3bqGxd1-0PEVbrf8u9JaoRbKez=hDYb2koSOde5WO34RA@mail.gmail.com
Whole thread
In response to Re: Way to access LSN (for each transaction) by directly talking to postgres?  (Michael Paquier <michael.paquier@gmail.com>)
List pgsql-hackers
Sorry I forgot to reply. Thanks! using decoding plugins works great

On Wed, Aug 3, 2016 at 8:37 PM, Michael Paquier <michael.paquier@gmail.com> wrote:
On Thu, Aug 4, 2016 at 3:02 AM, Joshua Bay <joshuabay93@gmail.com> wrote:
> Could you please tell me how I can get LSN of each transaction at decoder
> plugin?

Craig already gave you hints, but here are more. You will need to hack
your own plugin. You could just use the one in contrib/test_decoding,
remove most of its code, and use the commit callback to issue the LSN
you are interested in. Note as well that when using
pg_logical_slot_peek_changes or pg_logical_slot_get_changes, you can
get a LSN location. Using test_decoding as a base, that's not a
complicated effort.
--
Michael

pgsql-hackers by date:

Previous
From: Joshua Bay
Date:
Subject: Most efficient way for libPQ .. PGresult serialization
Next
From: Ryan Murphy
Date:
Subject: Re: Patch: initdb: "'" for QUOTE_PATH (non-windows)