| From: | Aleksander Alekseev <aleksander(at)timescale(dot)com> |
|---|---|
| To: | Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Cc: | Maxim Orlov <orlovmg(at)gmail(dot)com>, Pavel Borisov <pashkin(dot)elfe(at)gmail(dot)com>, Japin Li <japinli(at)hotmail(dot)com>, Alexander Korotkov <aekorotkov(at)gmail(dot)com>, Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>, Ilya Anfimov <ilan(at)tzirechnoy(dot)com>, Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> |
| Subject: | Re: XID formatting and SLRU refactorings (was: Add 64-bit XIDs into PostgreSQL 15) |
| Date: | 2022-03-22 07:35:05 |
| Message-ID: | CAJ7c6TPocitQf71gBjRQUVgUMYNO4kfng5sJyEi8bpDMBRT3YQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi Peter,
> I think there needs to be a bit more soul searching here on how to
> handle that in the future and how to transition it. I don't think
> targeting this patch for PG15 is useful at this point.
The patches can be reordered so that we are still able to deliver SLRU
refactoring in PG15.
> As a more general point, I don't like plastering these bulky casts all
> over the place. Casts hide problems.
Regarding the casts, I don't like them either. I agree that it could
be a good idea to invest a little more time into figuring out if this
transit can be handled in a better way and deliver this change in the
next CF. However, if no one will be able to suggest a better
alternative, I think we should continue making progress here. The
32-bit XIDs are a major inconvenience for many users.
--
Best regards,
Aleksander Alekseev
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Masahiko Sawada | 2022-03-22 07:48:53 | Re: Add index scan progress to pg_stat_progress_vacuum |
| Previous Message | Imseih (AWS), Sami | 2022-03-22 07:27:32 | Re: Add index scan progress to pg_stat_progress_vacuum |