| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Bertrand Drouvot <bertranddrouvot(dot)pg(at)gmail(dot)com> |
| Cc: | Michael Paquier <michael(at)paquier(dot)xyz>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Remove useless pointer advance in StatsShmemInit() |
| Date: | 2025-12-02 20:00:39 |
| Message-ID: | zmsdnmcpfa3ck3s343in7yz5hzyuz6jlpyfvs2vgwgbum6focf@kkow5hfcybz6 |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
On 2025-12-02 07:40:44 +0000, Bertrand Drouvot wrote:
> From 2fefb69f1462ce1057bb5c3d07ed70c769ec961a Mon Sep 17 00:00:00 2001
> From: Bertrand Drouvot <bertranddrouvot(dot)pg(at)gmail(dot)com>
> Date: Sat, 22 Nov 2025 14:47:25 +0000
> Subject: [PATCH v1] Remove useless pointer updates
>
> Same idea as in commit 9b7eb6f02e8. Those pointers are updated but are not used
> after the updates, so let's remove the useless updates or document why we want
> to keep them.
I think this is a bad idea. To the degree that I think 9b7eb6f02e8 ought to be
reverted. All these changes do is to make future extensions of the relevant
code more failure prone. Omitting the pointer update means that the pointer
at the end points before the last "chunk", rather than at the end.
What's the point of this? Compilers are perfectly capable of removing a
trailing store if the updated value isn't ever used afterwards.
Greetings,
Andres
| From | Date | Subject | |
|---|---|---|---|
| Previous Message | Andres Freund | 2025-12-02 19:49:13 | Re: All-visible pages with valid prune xid are confusing |