Use PG_GETARG_TRANSACTIONID where appropriate
authorPeter Eisentraut <peter@eisentraut.org>
Mon, 2 Nov 2020 15:48:22 +0000 (16:48 +0100)
committerPeter Eisentraut <peter@eisentraut.org>
Mon, 2 Nov 2020 15:48:22 +0000 (16:48 +0100)
commitdd26a0ad760b11237d7ea9cda8ccccc1826c2c64
tree4e691c4f012ea5dedc1b0d5a7cc6850254f2cf2f
parent5b3dca096f8e504b73812f68716fb68dd1176d6d
Use PG_GETARG_TRANSACTIONID where appropriate

Some places were using PG_GETARG_UINT32 where PG_GETARG_TRANSACTIONID
would be more appropriate.  (Of course, they are the same internally,
so there is no externally visible effect.)  To do that, export
PG_GETARG_TRANSACTIONID outside of xid.c.  We also export
PG_RETURN_TRANSACTIONID for symmetry, even though there are currently
no external users.

Author: Ashutosh Bapat <ashutosh.bapat@2ndquadrant.com>
Discussion: https://www.postgresql.org/message-id/flat/d8f6bdd536df403b9b33816e9f7e0b9d@G08CNEXMBPEKD05.g08.fujitsu.local
src/backend/access/transam/commit_ts.c
src/backend/access/transam/multixact.c
src/backend/utils/adt/xid.c
src/include/fmgr.h