A patch for get origin from commit_ts.

From: "movead(dot)li(at)highgo(dot)ca" <movead(dot)li(at)highgo(dot)ca>
To: pgsql-hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: A patch for get origin from commit_ts.
Date: 2020-05-11 08:43:11
Message-ID: 2020051116430836450630@highgo.ca
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

Hello hackers,

I am researching about 'origin' in PostgreSQL, mainly it used in logical
decoding to filter transaction from non-local source. I notice that the
'origin' is stored in commit_ts so that I think we are possible to get 'origin'
of a transaction from commit_ts.

But I can not fond any code to get 'origin' from commit_ts, just like it is
producing data which nobody cares about. Can I know what's the purpose
of the 'origin' in commit_ts? Do you think we should add some support
to the careless data?

For example, I add a function to get 'origin' from commit_ts:
postgres=# select pg_xact_commit_origin('490');
(1 row)

postgres=# select pg_xact_commit_origin('491');
(1 row)


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

Attachment Content-Type Size
get_origin_from_commit_ts.patch application/octet-stream 1.5 KB


Browse pgsql-hackers by date

  From Date Subject
Next Message Antonin Houska 2020-05-11 08:44:14 Re: 2pc leaks fds
Previous Message Kyotaro Horiguchi 2020-05-11 08:13:54 Re: pg_regress cleans up tablespace twice.