Re: Change copyObject() to use typeof_unqual

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Jelte Fennema-Nio" <postgres(at)jeltef(dot)nl>
Cc: "Masahiko Sawada" <sawada(dot)mshk(at)gmail(dot)com>, "Peter Eisentraut" <peter(at)eisentraut(dot)org>, "pgsql-hackers" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Change copyObject() to use typeof_unqual
Date: 2026-03-17 15:05:04
Message-ID: 398055.1773759904@sss.pgh.pa.us
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

"Jelte Fennema-Nio" <postgres(at)jeltef(dot)nl> writes:
> On Tue Mar 17, 2026 at 3:39 AM CET, Tom Lane wrote:
>> While this version of clang doesn't like typeof_unqual, it does take
>> __typeof_unqual__. So maybe we were premature to decide that we
>> could prefer the typeof_unqual spelling.

> Hmmm, that makes sense. How about this patch to at least keep the
> all the logic related to this in one place? I was able to reproduce this
> error using the following flags, and this fixes the issue for me.

Seems reasonable, and I confirm that this fixes things for me on
Fedora 43.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Ayush Tiwari 2026-03-17 15:07:26 Re: Proposal: Prevent Primary/Standby SLRU divergence during MultiXact truncation
Previous Message Nathan Bossart 2026-03-17 15:01:42 Re: Add starelid, attnum to pg_stats and leverage this in pg_dump