|From:||Michael Paquier <michael(at)paquier(dot)xyz>|
|Subject:||pgsql: Include replication origins in SQL functions for commit timestam|
|Views:||Raw Message | Whole Thread | Download mbox | Resend email|
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
- 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
doc/src/sgml/func.sgml | 22 ++++-
src/backend/access/transam/commit_ts.c | 71 +++++++++++++++--
src/include/catalog/catversion.h | 2 +-
src/include/catalog/pg_proc.dat | 15 +++-
.../commit_ts/expected/commit_timestamp.out | 93 +++++++++++++++++++++-
.../commit_ts/expected/commit_timestamp_1.out | 75 ++++++++++++++++-
.../modules/commit_ts/sql/commit_timestamp.sql | 35 +++++++-
7 files changed, 295 insertions(+), 18 deletions(-)
|Next Message||Michael Paquier||2020-07-12 12:25:07||Re: pgsql: Include replication origins in SQL functions for commit timestam|
|Previous Message||Tom Lane||2020-07-11 18:21:36||pgsql: Avoid useless buffer allocations during binary COPY FROM.|