From: | "Andres Freund" <andres(at)anarazel(dot)de> |
---|---|
To: | pgsql-committers(at)lists(dot)postgresql(dot)org |
Subject: | Re: pgsql: SQL-standard function body |
Date: | 2021-04-08 14:56:10 |
Message-ID: | a5f3b343-f502-4d30-8db1-446db94502c2@www.fastmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
Hi,
On Thu, Apr 8, 2021, at 07:52, Tom Lane wrote:
> Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> > On 4/7/21 9:50 PM, Andres Freund wrote:
> >> I've wondered about that too. Perhaps we could reuse the pg_upgrade run?
>
> > Honestly I'd prefer it if we could get rid of the rerun of 'make check'
> > by pg_upgrade's test.sh and instead upgrade the data directory made by
> > the earlier 'make check' run if it's still there (which would mean we'd
> > need to stop it being deleted).
>
> Good idea as far as speeding check-world and buildfarm runs, but I wonder
> if we wouldn't be losing test coverage. Seeing the number of times that
> buildfarm runs have gotten through "make check" only to fail at the
> re-run in pg_upgrade, it seems clear to me that there is something
> different about the execution environment in the latter case. I've
> never been able to pin down quite what :-(
IIRC we made it run with fsync explicitly enabled. Which obviously will change timing somewhat substantially...
Andres
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2021-04-08 15:16:14 | pgsql: Fixes for query_id feature |
Previous Message | Tom Lane | 2021-04-08 14:52:16 | Re: pgsql: SQL-standard function body |