Re: Mark ItemPointer arguments as const thoughoutly

From: Chao Li <li(dot)evan(dot)chao(at)gmail(dot)com>
To: Peter Eisentraut <peter(at)eisentraut(dot)org>
Cc: Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Mark ItemPointer arguments as const thoughoutly
Date: 2025-10-30 14:18:24
Message-ID: 47D1025E-F163-4DF7-AD93-E84FF2DD7768@gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi Peter,

> On Oct 30, 2025, at 21:30, Peter Eisentraut <peter(at)eisentraut(dot)org> wrote:
>
> I have committed most of this patch.

Thank you so much for committing my patch and for your guidance. I’m still ramping up on PostgreSQL development, and your guidance has been super helpful to me.

>
> I didn't like the few places in itemptr.h where you changed an existing ItemPointerData* back to ItemPointer, so I left those out.
>
> More importantly, some of the proposed changes change the signatures of callback functions in the index or table AM APIs. (And also the documentation wasn't updated.) This would break source code compatibility with existing extensions that use those APIs. There are have been previous proposals like this in [0], [1] where the changes to those APIs were not committed. And your other patch 'Mark function arguments of type "Datum *" as "const Datum *" where possible' might have similar problems (although it looks like it's touching different places than [0] and [1]). So I left those changes out of what I committed.

I will revisit that patch once I am back from vacation.

Best regards,
--
Chao Li (Evan)
HighGo Software Co., Ltd.
https://www.highgo.com/

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Ilia Evdokimov 2025-10-30 14:35:24 Re: V18 change on EXPLAIN ANALYZE
Previous Message David E. Wheeler 2025-10-30 14:10:43 Re: abi-compliance-check failure due to recent changes to pg_{clear,restore}_{attribute,relation}_stats()