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: 2025-12-29 08:31:36
Message-ID: em030bc3ec-8636-4782-9a8c-8269447c8ec2@cybertec.at
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Greetings!
>> Changes:
>> - OID 5101 (verified available with unused_oids script)
>
>./unused_oids also states the following thing:
>Best practice is to start with a random choice in the range 8000-9999.

Oh, I misunderstood it completely. I thought one should go to 8K+ if
they
want a block of OIDs not just one. Thanks!
>
>
>We do an OID renumbering while in beta, so please use an OID in this
>range for the development of new patches. ;)

Cool! Will update the patch. Thanks for your input!

Best regards,
Pavlo

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Dmitry Koval 2025-12-29 08:43:00 Re: Assert when executing query on partitioned table
Previous Message Chao Li 2025-12-29 08:24:55 Re: Proposal: Cascade REPLICA IDENTITY changes to leaf partitions