Home > mailing lists

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

From	Simon Riggs
Subject	Re: A patch for get origin from commit_ts.
Date	June 30, 2020 15:58:17
Msg-id	CANP8+jJu-bta+4KBRDf2XKsHybDBY1Ew_zvcuoTdhES+ZWLGcQ@mail.gmail.com Whole thread Raw
In response to	Re: A patch for get origin from commit_ts. (Madan Kumar <madankumar1993@gmail.com>)
Responses	Re: A patch for get origin from commit_ts. (michael@paquier.xyz)
List	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/
Mission Critical Databases

From: Daniel Gustafsson
Date: 30 June 2020, 15:25:07
Subject: Re: Ought to use heap_multi_insert() for pg_attribute/depend insertions?

From: Fujii Masao
Date: 30 June 2020, 16:40:09
Subject: Re: track_planning causing performance regression