| From: | Sami Imseih <samimseih(at)gmail(dot)com> |
|---|---|
| To: | Michael Paquier <michael(at)paquier(dot)xyz> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: stats.sql fails during installcheck on mac |
| Date: | 2025-04-12 00:37:49 |
| Message-ID: | CAA5RZ0vGi5s58GUDy58Zj5_QSqO-tzzVaFm7yZp1nf5-CmvM2g@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> > what do you think of this? I think we should set fsync = on
> > at least for the part of the test that proceeds the 2 checkpoints and
> > set if back to off at the end of the tests for fsync stats. It is concerning
> > the tests for the fsync stats are not being exercised in
> > the buildfarm.
>
> One thing I fear here is the impact for animals with little capacity,
> like PIs and the like. On the other hand, I could just switch one of
> my animals to use fsync = on on at least one branch.
Yes, there should be some tests running for these stats,
so if it's possible to enable fsync on one or a few animals, that
will be better than nothing.
--
Sami
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David G. Johnston | 2025-04-12 01:13:45 | Re: n_ins_since_vacuum stats for aborted transactions |
| Previous Message | Sami Imseih | 2025-04-12 00:18:55 | Re: n_ins_since_vacuum stats for aborted transactions |