Quick Links

Re[2]: [PATCH] Add pg_current_vxact_id() function to expose virtual transaction IDs

From:	"Pavlo Golub" <pavlo(dot)golub(at)cybertec(dot)at>
To:	"Michael Paquier" <michael(at)paquier(dot)xyz>
Cc:	pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject:	Re[2]: [PATCH] Add pg_current_vxact_id() function to expose virtual transaction IDs
Date:	2026-01-06 12:47:08
Message-ID:	em865feff4-1744-4de5-80f3-314fa417765f@cybertec.at
Views:	Whole Thread \| Raw Message \| Download mbox \| Resend email
Thread:
Lists:	pgsql-hackers

Hello.

Attached is v2 of the pg_current_vxact_id() patch.
Changes in v2:
- Rebased on current master
- Changed OID from 5101 to 9538 (following unused_oids best practice
recommendation to use the 8000-9999 range for patch development)

Best regards,
Pavlo Golub

Attachment	Content-Type	Size
v2-0001-add-pg_current_vxact_id-function.patch	application/octet-stream	7.3 KB

In response to

Re: [PATCH] Add pg_current_vxact_id() function to expose virtual transaction IDs at 2025-12-29 00:14:31 from Michael Paquier

Responses

Re: Re[2]: [PATCH] Add pg_current_vxact_id() function to expose virtual transaction IDs at 2026-01-06 13:59:18 from Henson Choi

Browse pgsql-hackers by date

	From	Date	Subject
Next Message	Xuneng Zhou	2026-01-06 13:12:41	Re: Implement waiting for wal lsn replay: reloaded
Previous Message	Shlok Kyal	2026-01-06 12:43:17	Re: Skipping schema changes in publication