Horton

Re: A patch for get origin from commit_ts.

movead.li@highgo.ca <movead.li@highgo.ca>

View thread View on postgr.es
From: "movead.li@highgo.ca" <movead.li@highgo.ca>
To: michael <michael@paquier.xyz>
Cc: pgsql-hackers <pgsql-hackers@lists.postgresql.org>
Date: 2020-05-13T08:29:19Z
Lists: pgsql-hackers

Attachments

>I have not thought about this matter, but it seems to me that you
>should add this patch to the upcoming commit fest for evaluation:
>https://commitfest.postgresql.org/28/ 
Thanks.

I think about it more detailed, and find it's better to show the 'roident'
other than 'roname'. Because an old 'roident' value will be used
immediately after dropped, and a new patch attached with test case
and documentation.

============================================
SELECT pg_xact_commit_origin('490');
 pg_xact_commit_origin 
-----------------------
                     1
(1 row)

SELECT pg_xact_commit_origin('491');
 pg_xact_commit_origin 
-----------------------
                     2
(1 row)
============================================




Regards,
Highgo Software (Canada/China/Pakistan) 
URL : www.highgo.ca 
EMAIL: mailto:movead(dot)li(at)highgo(dot)ca

Commits

  1. Include replication origins in SQL functions for commit timestamp

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