From: Tom Lane <tgl@sss.pgh.pa.us>
To: Alvaro Herrera <alvherre@2ndquadrant.com>
Cc: pgsql-hackers@lists.postgresql.org
Cc: 2q-andrew@alvin.alvh.no-ip.org
Subject: Re: pgsql: Fix "base" snapshot handling in logical decoding
Date: Fri, 29 Jun 2018 19:02:04 -0400
Message-ID: <27276.1530313324@sss.pgh.pa.us> (raw)
In-Reply-To: <20180629225055.cy3e4ecayibwr5rd@alvherre.pgsql>
References: <20180629225055.cy3e4ecayibwr5rd@alvherre.pgsql>
Alvaro Herrera <alvherre@2ndquadrant.com> writes:
>> On 2018-Jun-28, Tom Lane wrote:
>>> According to buildfarm member friarbird, and as confirmed here,
>>> the contrib/test_decoding/specs/oldest_xmin.spec test added by this
>>> commit fails under CLOBBER_CACHE_ALWAYS.
> I suppose 60 seconds (isolationtester's default timeout) is just not
> enough time for those machines. We could increase it to 180 seconds and
> see if that's enough to make them pass ...
What I want to know is why this test is doing a database-wide VACUUM FULL
in the first place. If that isn't profligate wastage of testing cycles,
why 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, alvherre@2ndquadrant.com, pgsql-hackers@lists.postgresql.org, 2q-andrew@alvin.alvh.no-ip.org
Subject: Re: pgsql: Fix "base" snapshot handling in logical decoding
In-Reply-To: <27276.1530313324@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