Re: get rid of Pointer type, mostly

From: David Geier <geidav(dot)pg(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: 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-11-24 18:46:27
Message-ID: 646aa41b-9810-442e-9a5a-69a5604190d4@gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

I'm in big favor of this change. Such types just cover up what's really
going on and make reading the code more difficult than needed,
especially for people new to the code base.

On 24.11.2025 19:26, Tom Lane wrote:
> Robert Haas <robertmhaas(at)gmail(dot)com> writes:

> I can follow the argument that using the native type "void *" is
> better, since every C programmer must know that already. But you
> cannot argue for this patch on that ground unless Pointer goes away
> entirely. I don't understand leaving it in place for GIN. It's
> not like GIN indexes are some hoary backwater that nobody pays
> attention to.

+1

The GIN code makes use of pointer but src/backend/access/gin only has 29
occurrences. If you like I can help out fixing up the GIN code and share
a page here. Let me know.

--
David Geier

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Masahiko Sawada 2025-11-24 18:48:19 Re: Assertion failure in SnapBuildInitialSnapshot()
Previous Message Nathan Bossart 2025-11-24 18:43:28 Re: Remove useless casting to the same type