Re: Change copyObject() to use typeof_unqual - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Change copyObject() to use typeof_unqual
Date
Msg-id 2191112.1773612810@sss.pgh.pa.us
Whole thread Raw
In response to Re: Change copyObject() to use typeof_unqual  ("Jelte Fennema-Nio" <postgres@jeltef.nl>)
Responses Re: Change copyObject() to use typeof_unqual
List pgsql-hackers
"Jelte Fennema-Nio" <postgres@jeltef.nl> writes:
> If not, then I'm starting to think that actually checking support for
> this feature for CLANG is probably easier to understand (and less
> fragile) than combining all of these tricks together. Attached is a
> patch to do so. 

+1 for concept, but don't you need to fix meson.build too?

>> And alternative is that
>> we decide that we don't want to support this combination, meaning that
>> we would effectively require that clang is approximately as-old-or-newer
>> than gcc.

> Given that Tom seems to have reproduced this on Fedora 40, it sounds
> like we should fix it.

Yeah.  Given Fedora's development cycle, it is a certainty that they
shipped gcc and clang versions no more than a couple months different
in age.  So even if we wanted to adopt the restriction Peter suggests,
there are not-very-old systems on which it fails.

            regards, tom lane



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Save a few bytes per CatCTup
Next
From: Michael Paquier
Date:
Subject: Re: Report bytes and transactions actually sent downtream