Horton

Re: A patch for get origin from commit_ts.

Simon Riggs <simon@2ndquadrant.com>

View thread View on postgr.es
From: Simon Riggs <simon@2ndquadrant.com>
To: Madan Kumar <madankumar1993@gmail.com>
Cc: "movead.li@highgo.ca" <movead.li@highgo.ca>, michael <michael@paquier.xyz>, pgsql-hackers <pgsql-hackers@lists.postgresql.org>, Craig Ringer <craig@2ndquadrant.com>, Petr Jelinek <petr@2ndquadrant.com>, Álvaro Herrera <alvherre@2ndquadrant.com>, Andres Freund <andres@anarazel.de>, soumyadeep2007@gmail.com
Date: 2020-06-30T12:58:17Z
Lists: pgsql-hackers 
On Tue, 30 Jun 2020 at 02:17, Madan Kumar <madankumar1993@gmail.com> wrote:


> We already have pg_xact_commit_timestamp() that returns the timestamp of
> the commit.


Yes, pg_xact_commit_origin() is a good name for an additional function. +1
for this.


> 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.

-- 
Simon Riggs                http://www.2ndQuadrant.com/
<http://www.2ndquadrant.com/>
Mission Critical Databases

Commits

  1. Include replication origins in SQL functions for commit timestamp

  2. Create a script that can renumber manually-assigned OIDs.