Re: Way to access LSN (for each transaction) by directly talking to postgres?

From: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
To: Joshua Bay <joshuabay93(at)gmail(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Craig Ringer <craig(at)2ndquadrant(dot)com>, Fabrízio Mello <fabriziomello(at)gmail(dot)com>
Subject: Re: Way to access LSN (for each transaction) by directly talking to postgres?
Date: 2016-08-04 00:37:02
Message-ID: CAB7nPqS6zSCvbqJyOZFTpfBq7EerG4F-9QUsPzz40k0bz1eBSA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Aug 4, 2016 at 3:02 AM, Joshua Bay <joshuabay93(at)gmail(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2016-08-04 00:40:31 Re: Implementing full UTF-8 support (aka supporting 0x00)
Previous Message Bruce Momjian 2016-08-04 00:34:02 Re: Lossy Index Tuple Enhancement (LITE)