Date: Thu, 9 Mar 2023 06:51:31 -0600
From: Justin Pryzby <pryzby@telsasoft.com>
To: Andres Freund <andres@anarazel.de>
Cc: Melanie Plageman <melanieplageman@gmail.com>,
	Kyotaro Horiguchi <horikyota.ntt@gmail.com>, tgl@sss.pgh.pa.us,
	vignesh21@gmail.com, lukas@fittl.com, alvherre@alvh.no-ip.org,
	magnus@hagander.net, pgsql-hackers@postgresql.org,
	thomas.munro@gmail.com, m.sakrejda@gmail.com
Subject: Re: pg_stat_bgwriter.buffers_backend is pretty meaningless (and
 more?)
Message-ID: <ZAnWU8WbXEDjrfUE@telsasoft.com>
References: <20230211182437.ype5tk3awen2htvw@awork3.anarazel.de>
 <3039228.1677972069@sss.pgh.pa.us>
 <20230306.152425.316894602450485455.horikyota.ntt@gmail.com>
 <20230306.154843.178021884584228317.horikyota.ntt@gmail.com>
 <CAAKRu_ZRKp-zDCSVk9p8XE=ZKTn3WiJD6Mt=n=eSPQ7Kg-=HRw@mail.gmail.com>
 <20230306190919.ai6mxdq3sygyyths@awork3.anarazel.de>
 <20230306192409.daz5ivq4mbbr2ye7@liskov>
 <20230306193404.3btuacgc6um33mt2@awork3.anarazel.de>
 <CAAKRu_ZmAhCGzk2GkNeMHTu0Oh=rtNKU7Q+fkzLs-PZBp1sicg@mail.gmail.com>
 <20230307181844.hxnlfi3wa5lm7sm2@awork3.anarazel.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20230307181844.hxnlfi3wa5lm7sm2@awork3.anarazel.de>
Archived-At: 
 <https://www.postgresql.org/message-id/ZAnWU8WbXEDjrfUE%40telsasoft.com>
Precedence: bulk

On Tue, Mar 07, 2023 at 10:18:44AM -0800, Andres Freund wrote:
> Hi,
> 
> On 2023-03-06 15:21:14 -0500, Melanie Plageman wrote:
> > Good point. Attached is what you suggested. I committed the transaction
> > before the drop table so that the statistics would be visible when we
> > queried pg_stat_io.
> 
> Pushed, thanks for the report, analysis and fix, Tom, Horiguchi-san, Melanie.

There's a 2nd portion of the test that's still flapping, at least on
cirrusci.

The issue that Tom mentioned is at:
 SELECT :io_sum_shared_after_writes > :io_sum_shared_before_writes;

But what I've seen on cirrusci is at:
 SELECT :io_sum_shared_after_writes > :io_sum_shared_before_writes;

https://api.cirrus-ci.com/v1/artifact/task/6701069548388352/log/src/test/recovery/tmp_check/regression.diffs
https://api.cirrus-ci.com/v1/artifact/task/5355168397524992/log/src/test/recovery/tmp_check/regression.diffs
https://api.cirrus-ci.com/v1/artifact/task/6142435751886848/testrun/build/testrun/recovery/027_stream_regress/log/regress_log_027_stream_regress

It'd be neat if cfbot could show a histogram of test failures, although
I'm not entirely sure what granularity would be most useful: the test
that failed (027_regress) or the way it failed (:after_write >
:before_writes).  Maybe it's enough to show the test, with links to its
recent failures.

-- 
Justin