Re: Add 64-bit XIDs into PostgreSQL 15

Pavel Borisov <pashkin.elfe@gmail.com>

From: Pavel Borisov <pashkin.elfe@gmail.com>

To: Alexander Korotkov <aekorotkov@gmail.com>

Cc: Aleksander Alekseev <aleksander@timescale.com>, Andres Freund <andres@anarazel.de>, Ilya Anfimov <ilan@tzirechnoy.com>, Postgres hackers <pgsql-hackers@lists.postgresql.org>, pgsql-hackers <pgsql-hackers@postgresql.org>

Date: 2022-03-03T13:40:53Z

Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

Add SLRU tests for 64-bit page case
- a60b8a58f435 17.0 landed
Make use FullTransactionId in 2PC filenames
- 5a1dfde8334b 17.0 landed
Use larger segment file names for pg_notify
- 2cdf131c46e6 17.0 landed
Index SLRUs by 64-bit integers rather than by 32-bit integers
- 4ed8f0913bfd 17.0 landed

>
> > BTW messages with patches in this thread are always invoke manual spam
> moderation and we need to wait for ~3 hours before the message with patch
> becomes visible in the hackers thread. Now when I've already answered
> Alexander's letter with v10 patch the very message (and a patch) I've
> answered is still not visible in the thread and to CFbot.
> >
> > Can something be done in hackers' moderation engine to make new versions
> patches become visible hassle-free?
>
> Is your email address subscribed to the pgsql-hackers mailing list?
> AFAIK, moderation is only applied for non-subscribers.
>
Hi, Alexander!

Yes, it is in the list. The problem is that patch is over 1Mb. So it
strictly goes through moderation. And this is unchanged for 2 months
already.
I was advised to use .gz, which I will do next time.

I've requested increasing threshold to 2 MB [1]

[1]
https://www.postgresql.org/message-id/flat/CALT9ZEGbAR84q_emsf1TUMPqXT%3Dc8CxN16g-HQCxgkLzekM%2BQg%40mail.gmail.com
--
Best regards,
Pavel Borisov

Postgres Professional: http://postgrespro.com <http://www.postgrespro.com>