Re: stats.sql fails during installcheck on mac

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Sami Imseih <samimseih(at)gmail(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: stats.sql fails during installcheck on mac
Date: 2025-04-10 22:36:24
Message-ID: 674368.1744324584@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Sami Imseih <samimseih(at)gmail(dot)com> writes:
> When running "make installcheck" on my mac, I ran into a failure:

> @@ -1459,7 +1459,7 @@
> OR :io_sum_wal_normal_after_fsyncs > :io_sum_wal_normal_before_fsyncs;
> ?column?
> ----------
> - t
> + f
> (1 row)

Hmm, that's a little nasty, because it's not showing up in the
buildfarm. It appears from a little testing that the issue only
manifests if you have fsync = on, which we generally don't on
buildfarm animals.

That concerns me independently of this specific failure, because
it calls into question how realistic our testing of things like
fsync statistics really is.

Anyway, back to the patch: there are multiple places in
stats.sql that are effectively disabling tests if fsync = off,
not only this one. Why does only this one need the exception?
Should we be rethinking or tightening some of the others?

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Daniel Gustafsson 2025-04-10 22:38:02 Re: Add missing PGDLLIMPORT markings
Previous Message Andres Freund 2025-04-10 22:27:26 Re: MergeJoin beats HashJoin in the case of multiple hash clauses