Re: get rid of Pointer type, mostly

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: 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:26:03
Message-ID: 970261.1764008763@sss.pgh.pa.us
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> But if it were up to me, I'd rip out Pointer completely, because
> reading code that uses the native C type names is easier for me than
> reading code that substitutes other notation.

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.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Nathan Bossart 2025-11-24 18:36:25 Re: pgsql: Teach DSM registry to ERROR if attaching to an uninitialized ent
Previous Message Álvaro Herrera 2025-11-24 17:49:47 Re: Issues with ON CONFLICT UPDATE and REINDEX CONCURRENTLY