Re: XID formatting and SLRU refactorings (was: Add 64-bit XIDs into PostgreSQL 15)
| От | Pavel Borisov |
|---|---|
| Тема | Re: XID formatting and SLRU refactorings (was: Add 64-bit XIDs into PostgreSQL 15) |
| Дата | |
| Msg-id | CALT9ZEFSAkFqf1fH9dWv5QmbTQc7VBf=f5mCPSbRMT7rCAgMkw@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: XID formatting and SLRU refactorings (was: Add 64-bit XIDs into PostgreSQL 15) (Maxim Orlov <orlovmg@gmail.com>) |
| Ответы |
Re: XID formatting and SLRU refactorings (was: Add 64-bit XIDs into PostgreSQL 15)
|
| Список | 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
Pavel Borisov
В списке pgsql-hackers по дате отправления: