| 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-03 06:08:58 |
| Message-ID: | CAB7nPqTeapPmZMfPmpviXoeNMzoeUGATxU-Gu0Hm_841vpYaBg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Aug 3, 2016 at 3:00 PM, Michael Paquier
<michael(dot)paquier(at)gmail(dot)com> wrote:
> On Wed, Aug 3, 2016 at 12:37 PM, Joshua Bay <joshuabay93(at)gmail(dot)com> wrote:
>> Could you please let me know if there is a way to get LSN of each
>> transaction by directly communicating with Postgres server and NOT by
>> accessing logs.
>
> Logical decoding is one way.
And I just saw your other message... What I just meant here is that if
you use a decoder plugin that just emits information at transaction
begin/commit you can directly get this information. There is no need
to directly look at the WAL logs, the server does it for you. And it
offers a good cover regarding the information that has already been
consumed or not.
(Btw, avoid sending emails across multiple mailing lists, particularly
pgsql-committers which is not aimed for that).
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2016-08-03 07:20:46 | Re: Why we lost Uber as a user |
| Previous Message | Michael Paquier | 2016-08-03 06:05:20 | Re: Quorum commit for multiple synchronous replication. |