Re: XID formatting and SLRU refactorings (was: Add 64-bit XIDs into PostgreSQL 15) - Mailing list pgsql-hackers

From Pavel Borisov
Subject Re: XID formatting and SLRU refactorings (was: Add 64-bit XIDs into PostgreSQL 15)
Date
Msg-id CALT9ZEFSAkFqf1fH9dWv5QmbTQc7VBf=f5mCPSbRMT7rCAgMkw@mail.gmail.com
Whole thread Raw
In response to Re: XID formatting and SLRU refactorings (was: Add 64-bit XIDs into PostgreSQL 15)  (Maxim Orlov <orlovmg@gmail.com>)
Responses Re: XID formatting and SLRU refactorings (was: Add 64-bit XIDs into PostgreSQL 15)
List pgsql-hackers
Is there any reason to continue with two separate threads and CF entries ?
The original reason was to have a smaller patch for considerate late in v15.

But right now, it just seems to cause every update to imply two email messages
rather than one.

Since the patch is split into 0001, 0002, 0003, 0004+, both can continue in the
main thread.  The early patches can still be applied independently from each
later patch (the same as with any other patch series).
 
I see the main goal of this split is to make discussion of this (easier) thread separate to the discussion of a whole patchset which is expected to be more thorough. 

Also I see the chances of this thread to be committed into v16 to be much higher than of a main patch, which will be for v17 then.

Thanks for the advice to add git thread instead of patch posting. Will try to do this.
--
Best regards,
Pavel Borisov

pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: PG15 beta1 sort performance regression due to Generation context change
Next
From: Tom Lane
Date:
Subject: Re: make update-po@master stops at pg_upgrade