Horton

Re: Add 64-bit XIDs into PostgreSQL 15

Pavel Borisov <pashkin.elfe@gmail.com>

View thread
From: Pavel Borisov <pashkin.elfe@gmail.com>
To: Aleksander Alekseev <aleksander@timescale.com>
Cc: Postgres hackers <pgsql-hackers@lists.postgresql.org>, Justin Pryzby <pryzby@telsasoft.com>, Maxim Orlov <orlovmg@gmail.com>, Stephen Frost <sfrost@snowman.net>, Alexander Korotkov <aekorotkov@gmail.com>, Andres Freund <andres@anarazel.de>, Ilya Anfimov <ilan@tzirechnoy.com>
Date: 2022-07-18T09:23:42Z
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 →

  1. Add SLRU tests for 64-bit page case

  2. Make use FullTransactionId in 2PC filenames

  3. Use larger segment file names for pg_notify

  4. Index SLRUs by 64-bit integers rather than by 32-bit integers

Attachments

>
> > I can agree with you that sending rebased patches too often can be a
> little annoying. On the other hand, otherwise, it's just red in Cfbot. I
> suppose it's much easier and more comfortable to review the patches that at
> least apply cleanly and pass all tests. So if Cfbot is red for a long time
> I feel we need to send a rebased patchset anyway.
> >
> > I'll try to not doing this too often but frankly, I don't see a better
> alternative at the moment.
>
> Considering the overall activity on the mailing list personally I
> don't see a problem here. Several extra emails don't bother me at all,
> but I would like to see a green cfbot report for an open item in the
> CF application. Otherwise someone will complain that the patch doesn't
> apply anymore and the result will be the same as for sending an
> updated patch, except that we will receive at least two emails instead
> of one.
>
Hi, Alexander!
Agree with you. I also consider green cfbot entry important. So PFA rebased
v43.

-- 
Best regards,
Pavel Borisov