Re: get rid of Pointer type, mostly

From: David Geier <geidav(dot)pg(at)gmail(dot)com>
To: Chao Li <li(dot)evan(dot)chao(at)gmail(dot)com>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Peter Eisentraut <peter(at)eisentraut(dot)org>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: get rid of Pointer type, mostly
Date: 2025-12-08 11:51:05
Message-ID: 127522fb-594d-4b88-8f4b-27f4aae60237@gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 08.12.2025 11:53, Chao Li wrote:
>
>
>> On Dec 8, 2025, at 18:25, David Geier <geidav(dot)pg(at)gmail(dot)com> wrote:
>>
>> Hi Peter,
>>> I went with your proposal of GinExtraPointer. See attached patch. It's
>>> based on the series of patches from Peter's initial mail. I've included
>>> the removal of the Pointer typedef in the same patch.
>>
>> It seems to me that we reached agreement. Are you planning to still
>> apply these patches?
>>
>
> Basically I am not against this patch, as 756a43689324b473ee07549a6eb7a53a203df5ad has done similar changes.
>
> What I want to understand is that why do we delete Pointer and add GinExtraPointer?
>
> ```
> -/*
> - * Pointer
> - * Variable holding address of any memory resident object.
> - * (obsolescent; use void * or char *)
> - */
> -typedef void *Pointer;
> ```
>
> And
> ```
> +typedef void *GinExtraPointer;
> ```
>
> They both are underlying “void *”. Are we expecting to improve code readability? More specific maybe?
>
Yes, because otherwise you have void *** in the GIN code.

Please check the thread for more details.

--
David Geier

In response to

Browse pgsql-hackers by date

  From Date Subject
Previous Message Dilip Kumar 2025-12-08 11:45:37 Re: Proposal: Conflict log history table for Logical Replication