Re: clang bug affecting greenfly

From: Álvaro Herrera <alvherre(at)kurilemu(dot)de>
To: Greg Burd <greg(at)burd(dot)me>
Cc: John Naylor <johncnaylorls(at)gmail(dot)com>, Nathan Bossart <nathandbossart(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Andrew Dunstan <andrew(at)dunslane(dot)net>
Subject: Re: clang bug affecting greenfly
Date: 2026-03-30 16:14:27
Message-ID: 202603301608.bpaforgfquc3@alvherre.pgsql
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi Greg,

On 2026-Mar-30, Greg Burd wrote:

> All fair points. I've changed greenfly to use GCC 13.3.0, thanks for
> the suggestion.

Hmm, the 'update_personality.pl' script suplied with the buildfarm
client script allows you to change the compiler version, but not the
compiler itself -- the rationale being that a machine with a different
compiler should be a different animal. So I suggest to put greenfly to
rest until the clang situation is resolved (at which time you're welcome
to turn it back on), and request a new animal to use in the same machine
running gcc. Right now, greenfly is reporting that it is running clang
13.3.0, which AFAIK makes is inconsistent.

--
Álvaro Herrera 48°01'N 7°57'E — https://www.EnterpriseDB.com/
"Estoy de acuerdo contigo en que la verdad absoluta no existe...
El problema es que la mentira sí existe y tu estás mintiendo" (G. Lama)

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Anton A. Melnikov 2026-03-30 16:19:41 Re: [BUG] Excessive memory usage with update on STORED generated columns.
Previous Message Tomas Vondra 2026-03-30 16:11:17 Re: Adding locks statistics