Re: Way to access LSN (for each transaction) by directly talking to postgres?
От | Michael Paquier |
---|---|
Тема | Re: Way to access LSN (for each transaction) by directly talking to postgres? |
Дата | |
Msg-id | CAB7nPqTeapPmZMfPmpviXoeNMzoeUGATxU-Gu0Hm_841vpYaBg@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Way to access LSN (for each transaction) by directly talking to postgres? (Michael Paquier <michael.paquier@gmail.com>) |
Ответы |
Re: Way to access LSN (for each transaction) by directly talking to postgres?
|
Список | pgsql-hackers |
On Wed, Aug 3, 2016 at 3:00 PM, Michael Paquier <michael.paquier@gmail.com> wrote: > On Wed, Aug 3, 2016 at 12:37 PM, Joshua Bay <joshuabay93@gmail.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
В списке pgsql-hackers по дате отправления: