Re: Change copyObject() to use typeof_unqual

From: Robins Tharakan <tharakan(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Álvaro Herrera <alvherre(at)kurilemu(dot)de>, Peter Eisentraut <peter(at)eisentraut(dot)org>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Jelte Fennema-Nio <postgres(at)jeltef(dot)nl>, tharar(at)amazon(dot)com
Subject: Re: Change copyObject() to use typeof_unqual
Date: 2026-06-17 11:45:45
Message-ID: CAEP4nAzaBGyVVX9YbaCJVymDsvT-NivFVe9hfPsyT9u3DM2FfQ@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

On Sun, 14 Jun 2026 at 01:27, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> =?utf-8?Q?=C3=81lvaro?= Herrera <alvherre(at)kurilemu(dot)de> writes:
> > For some reason, a couple of animals running gcc-15 or newer
> > (leafhopper, massasauga, parula) appear to be failing now because of
> > this.
>
> They just started failing a day or two ago, so it's hard to blame
> it on any code change we made. I see that all three of those animals
> are using "experimental" nightly builds of gcc, so it's reasonable to
> assume that gcc's git tip is broken. Or maybe something needs updated
> in the recipe for replacing their gcc builds.

Earlier, since gcc HEAD was too noisy, I moved them all to gcc v15
assuming it'd be better. The gcc build script has been stable and there's
been no change in any of the machines recently, so I also wouldn't be
surprised if it is gcc again.

For now, I've taken them all offline and unless someone has a better
idea, I'll switch them to stay pinned to the recentmost gcc release
version - rationale being that if a tagged gcc release is buggy, it
may be interesting to know about.

-
robins | robins.in

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jelte Fennema-Nio 2026-06-17 12:11:24 Re: Change copyObject() to use typeof_unqual
Previous Message Nisha Moond 2026-06-17 11:42:22 Re: [PATCH] Preserve replication origin OIDs in pg_upgrade