From: Tom Lane <tgl@sss.pgh.pa.us>
To: Kyotaro Horiguchi <horikyota.ntt@gmail.com>
Cc: alvherre@alvh.no-ip.org
Cc: pgsql-committers@lists.postgresql.org
Subject: Re: pgsql: Remove testing for precise LSN/reserved bytes in new TAP test
Date: Thu, 09 Apr 2020 17:31:59 -0400
Message-ID: <12174.1586467919@sss.pgh.pa.us> (raw)
In-Reply-To: <20200409.101339.1252894237035894186.horikyota.ntt@gmail.com>
References: <E1jM1Sa-0003mS-99@gemulon.postgresql.org>
<20200408.144452.1031907626229663626.horikyota.ntt@gmail.com>
<20200409.101339.1252894237035894186.horikyota.ntt@gmail.com>
Kyotaro Horiguchi <horikyota.ntt@gmail.com> writes:
>> Sorry for the wrong test file.
>> Checking in lower precision would be sufficient.
> I noticed that prailiedog failed in another mode.
Yeah. We have at least four different buildfarm members complaining
about this test case. I took this patch and further lobotomized the
tests by removing *all* dependencies on restart_lsn and
pg_current_wal_lsn(). If anybody wants to put any of that back,
the burden of proof will be on them to show why we should believe
the results will be stable, not for the buildfarm to demonstrate
that they're not.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-committers@postgresql.org
Cc: tgl@sss.pgh.pa.us, horikyota.ntt@gmail.com, alvherre@alvh.no-ip.org, pgsql-committers@lists.postgresql.org
Subject: Re: pgsql: Remove testing for precise LSN/reserved bytes in new TAP test
In-Reply-To: <12174.1586467919@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox