From: | Peter Geoghegan <pg(at)bowt(dot)ie> |
---|---|
To: | Michael Paquier <michael(at)paquier(dot)xyz> |
Cc: | Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: amcheck eating most of the runtime with wal_consistency_checking |
Date: | 2021-04-20 02:58:37 |
Message-ID: | CAH2-Wz=VRCzmTC5-64ek82_db+XY7Zvy=iuq0bnmT=1Le-Mwww@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, Apr 19, 2021 at 7:50 PM Michael Paquier <michael(at)paquier(dot)xyz> wrote:
> While testing wal_consistency_checking, I have noticed that by far
> most of the runtime is spent within the regression test check_btree on
> the series of three queries inserting each 100k tuples. This also
> eats most of the run time of the test on HEAD. Could we for example
> consider inserting less tuples with a lower fillfactor to reduce the
> runtime of the test without impacting its coverage in a meaningful
> way?
I don't see much point. wal_consistency_checking is intrinsically a
tool that increases the volume of WAL by a large multiple. Plus you
yourself only run it once a year.
I run it much more often than once a year (maybe once every 2 - 3
months), but I haven't noticed this at all.
--
Peter Geoghegan
From | Date | Subject | |
---|---|---|---|
Next Message | David Rowley | 2021-04-20 03:00:53 | Re: Reduce the number of special cases to build contrib modules on windows |
Previous Message | Pavel Stehule | 2021-04-20 02:57:00 | Re: 2 questions about volatile attribute of pg_proc. |