Include replication origins in SQL functions for commit timestamp
Michael Paquier <michael@paquier.xyz>
Include replication origins in SQL functions for commit timestamp This includes two changes: - Addition of a new function pg_xact_commit_timestamp_origin() able, for a given transaction ID, to return the commit timestamp and replication origin of this transaction. An equivalent function existed in pglogical. - Addition of the replication origin to pg_last_committed_xact(). The commit timestamp manager includes already APIs able to return the replication origin of a transaction on top of its commit timestamp, but the code paths for replication origins were never stressed as those functions have never looked for a replication origin, and the SQL functions available have never included this information since their introduction in 73c986a. While on it, refactor a test of modules/commit_ts/ to use tstzrange() to check that a transaction timestamp is within the wanted range, making the test a bit easier to read. Bump catalog version. Author: Movead Li Reviewed-by: Madan Kumar, Michael Paquier Discussion: https://postgr.es/m/2020051116430836450630@highgo.ca
Files
| Path | Change | +/− |
|---|---|---|
| doc/src/sgml/func.sgml | modified | +19 −3 |
| src/backend/access/transam/commit_ts.c | modified | +66 −5 |
| src/include/catalog/catversion.h | modified | +1 −1 |
| src/include/catalog/pg_proc.dat | modified | +12 −3 |
| src/test/modules/commit_ts/expected/commit_timestamp_1.out | modified | +74 −1 |
| src/test/modules/commit_ts/expected/commit_timestamp.out | modified | +89 −4 |
| src/test/modules/commit_ts/sql/commit_timestamp.sql | modified | +34 −1 |
Documentation touched
Discussion
- A patch for get origin from commit_ts. 31 messages · 2020-05-11 → 2020-07-12