| From: | "Greg Burd" <greg(at)burd(dot)me> |
|---|---|
| To: | Álvaro Herrera <alvherre(at)kurilemu(dot)de> |
| 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 17:17:38 |
| Message-ID: | 13247365-24ff-4607-85ef-6f425502c824@app.fastmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Mar 30, 2026, at 12:14 PM, Álvaro Herrera wrote:
> 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.
Interesting, I was just looking for a why to change that after discovering the update_personality.pl limitation.
Sure, I'll apply for a new animal and change greenfly back.
-greg
> --
> Á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)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2026-03-30 17:28:41 | Re: EXPLAIN: showing ReadStream / prefetch stats |
| Previous Message | Robert Treat | 2026-03-30 17:13:06 | Re: Add pg_stat_autovacuum_priority |