Re: A patch for get origin from commit_ts. - Mailing list pgsql-hackers

From michael@paquier.xyz
Subject Re: A patch for get origin from commit_ts.
Date
Msg-id 20200702015852.GE10408@paquier.xyz
Whole thread Raw
In response to Re: A patch for get origin from commit_ts.  (Simon Riggs <simon@2ndquadrant.com>)
Responses Re: A patch for get origin from commit_ts.  (Simon Riggs <simon@2ndquadrant.com>)
Re: A patch for get origin from commit_ts.  (Petr Jelinek <petr@2ndquadrant.com>)
List pgsql-hackers
On Tue, Jun 30, 2020 at 01:58:17PM +0100, Simon Riggs wrote:
> On Tue, 30 Jun 2020 at 02:17, Madan Kumar <madankumar1993@gmail.com> wrote:
>> It may be better to have one single function returning both
>> timestamp and origin for a given transaction ID.
>
> No need to change existing APIs.

Adding a new function able to return both fields at the same time does
not imply that we'd remove the original one, it just implies that we
would be able to retrieve both fields with a single call of
TransactionIdGetCommitTsData(), saving from an extra CommitTsSLRULock
taken, etc.  That's actually what pglogical does with
its pglogical_xact_commit_timestamp_origin() in
pglogical_functions.c.  So adding one function able to return one
tuple with the two fields, without removing the existing
pg_xact_commit_timestamp() makes the most sense, no?
--
Michael

Attachment

pgsql-hackers by date:

Previous
From: michael@paquier.xyz
Date:
Subject: Re: A patch for get origin from commit_ts.
Next
From: Kyotaro Horiguchi
Date:
Subject: Re: Asynchronous Append on postgres_fdw nodes.