pg.ddx.io  pgsql-committers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Alvaro Herrera <alvherre@2ndquadrant.com>
To: Kyotaro Horiguchi <horikyota.ntt@gmail.com>
Cc: tgl@sss.pgh.pa.us
Cc: pgsql-committers@lists.postgresql.org
Subject: Re: pgsql: Remove testing for precise LSN/reserved bytes in new TAP test
Date: Fri, 10 Apr 2020 11:23:45 -0400
Message-ID: <20200410152345.GA13282@alvherre.pgsql> (raw)
In-Reply-To: <20200410.113332.337305854143176317.horikyota.ntt@gmail.com>

On 2020-Apr-10, Kyotaro Horiguchi wrote:

> > 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.
> 
> I think the significant part of the test is wal_status. So I'm not
> eager to get it back.

Agreed.  Thanks for stabilizing it.

-- 
Álvaro Herrera                https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services





view thread (6+ messages)

Message-ID: <20200410152345.GA13282@alvherre.pgsql>
Permalink:  ../20200410152345.GA13282@alvherre.pgsql/
Also on:    postgresql.org/message-id/20200410152345.GA13282@alvherre.pgsql

 · 

reply

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: alvherre@2ndquadrant.com, horikyota.ntt@gmail.com, tgl@sss.pgh.pa.us, pgsql-committers@lists.postgresql.org
  Subject: Re: pgsql: Remove testing for precise LSN/reserved bytes in new TAP test
  In-Reply-To: <20200410152345.GA13282@alvherre.pgsql>

* 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