Re: why is pg_upgrade's regression run so slow?

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: why is pg_upgrade's regression run so slow?
Date: 2024-07-28 19:43:23
Message-ID: 3c205102-a566-46ae-b16d-bea0dd708060@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


On 2024-07-27 Sa 6:48 PM, Tom Lane wrote:
> Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
>> On 2024-07-27 Sa 10:20 AM, Tom Lane wrote:
>>> Just to add some more fuel to the fire: I do *not* observe such an
>>> effect on my own animals.
>> The culprit appears to be meson. When I tested running crake with
>> "using_meson => 0" I got results in line with yours.
> Interesting. Maybe meson is over-aggressively trying to run these
> test suites in parallel?

Maybe, IDK. Meanwhile, I disabled "debug_parallel_query = regress" on
HEAD for fairywren and drongo -  fairwren has just gone green, and I
expect drongo will when it reports in a few hours.

I'm at a loss for an explanation.

cheers

andrew

--
Andrew Dunstan
EDB: https://www.enterprisedb.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jeff Davis 2024-07-28 20:02:20 Re: Speed up collation cache
Previous Message Dean Rasheed 2024-07-28 19:18:07 Re: Optimize mul_var() for var1ndigits >= 8