Re: Should we add xid_current() or a int8->xid cast?

Thomas Munro <thomas.munro@gmail.com>

From: Thomas Munro <thomas.munro@gmail.com>

To: Fujii Masao <masao.fujii@oss.nttdata.com>

Cc: Mark Dilger <hornschnorter@gmail.com>, pgsql-hackers <pgsql-hackers@postgresql.org>, Andres Freund <andres@anarazel.de>, Tom Lane <tgl@sss.pgh.pa.us>

Date: 2020-04-02T03:21:34Z

Lists: pgsql-hackers

Attachments

v8-0001-Add-SQL-type-xid8-to-expose-FullTransactionId-to-.patch (text/x-patch) patch v8-0001
v8-0002-Introduce-xid8_XXX-functions-to-replace-txid_XXX.patch (text/x-patch) patch v8-0002

On Sat, Mar 21, 2020 at 11:14 AM Thomas Munro <thomas.munro@gmail.com> wrote:
> * updated OIDs to avoid collisions
> * added btequalimage to btree/xid8_ops

Here's the version I'm planning to commit tomorrow, if no one objects.  Changes:

* txid.c renamed to xid8funcs.c
* remaining traces of "txid" replaced various internal identifiers
* s/backwards compatible/backward compatible/ in funcs.sgml (en_GB -> en_US)

Commits

Introduce xid8-based functions to replace txid_XXX.
- 4c04be9b05ad 13.0 landed
Add SQL type xid8 to expose FullTransactionId to users.
- aeec457de8a8 13.0 landed
Replace the former method of determining snapshot xmax --- to wit, calling
- 6bd4f401b0cb 8.3.0 cited