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

From Michael Paquier
Subject Re: A patch for get origin from commit_ts.
Date
Msg-id 20200703051059.GB1729@paquier.xyz
Whole thread Raw
In response to Re: A patch for get origin from commit_ts.  (Petr Jelinek <petr@2ndquadrant.com>)
Responses Re: A patch for get origin from commit_ts.
List pgsql-hackers
On Thu, Jul 02, 2020 at 10:12:02AM +0200, Petr Jelinek wrote:
> On 02/07/2020 03:58, michael@paquier.xyz wrote:
>> 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?
>
> Agreed, sounds reasonable.

Thanks.  Movead, please note that the patch is waiting on author?
Could you send an update if you think that those changes make sense?
--
Michael

Attachment

pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: Read access for pg_monitor to pg_replication_origin_status view
Next
From: "Andrey V. Lepikhov"
Date:
Subject: Re: [POC] Fast COPY FROM command for the table with foreign partitions