| From: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
|---|---|
| To: | Madan Kumar <madankumar1993(at)gmail(dot)com> |
| Cc: | "movead(dot)li(at)highgo(dot)ca" <movead(dot)li(at)highgo(dot)ca>, michael <michael(at)paquier(dot)xyz>, pgsql-hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Craig Ringer <craig(at)2ndquadrant(dot)com>, Petr Jelinek <petr(at)2ndquadrant(dot)com>, Álvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, soumyadeep2007(at)gmail(dot)com |
| Subject: | Re: A patch for get origin from commit_ts. |
| Date: | 2020-06-30 12:58:17 |
| Message-ID: | CANP8+jJu-bta+4KBRDf2XKsHybDBY1Ew_zvcuoTdhES+ZWLGcQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, 30 Jun 2020 at 02:17, Madan Kumar <madankumar1993(at)gmail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fujii Masao | 2020-06-30 13:40:09 | Re: track_planning causing performance regression |
| Previous Message | Daniel Gustafsson | 2020-06-30 12:25:07 | Re: Ought to use heap_multi_insert() for pg_attribute/depend insertions? |