| From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
|---|---|
| To: | James Coleman <jtc331(at)gmail(dot)com> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Add last commit LSN to pg_last_committed_xact() |
| Date: | 2022-01-18 18:52:26 |
| Message-ID: | 202201181852.paa7sw4hzkuc@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2022-Jan-18, James Coleman wrote:
> Reading the code it seems the only usage (besides
> the boolean activation status also stored there) is in
> TransactionIdGetCommitTsData, and the only consumers of that in core
> appear to be the SQL callable functions to get the latest commit info.
> It is in commit_ts.h though, so I'm guessing someone is using this
> externally (and maybe that's why the feature has the shape it does).
Logical replication is the intended consumer of that info, for the
purposes of conflict handling. I suppose pglogical uses it, but I don't
know that code myself.
[ ... greps ... ]
Yeah, that function is called from pglogical.
--
Álvaro Herrera Valdivia, Chile — https://www.EnterpriseDB.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2022-01-18 18:55:22 | Re: refactoring basebackup.c |
| Previous Message | Robert Haas | 2022-01-18 18:50:57 | pgsql: Modify pg_basebackup to use a new COPY subprotocol for base back |