Re: pgsql: Fix "base" snapshot handling in logical decoding

From: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org, 2q-andrew(at)alvin(dot)alvh(dot)no-ip(dot)org
Subject: Re: pgsql: Fix "base" snapshot handling in logical decoding
Date: 2018-06-29 22:29:06
Message-ID: 20180629222906.w5hqjgclmtk76v5i@alvherre.pgsql
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

On 2018-Jun-28, Tom Lane wrote:

> Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> writes:
> > Fix "base" snapshot handling in logical decoding
>
> 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.

Hm. Running this test under CLOBBER_CACHE_ALWAYS I see that the VACUUM
FULL step takes 31 seconds (and the test succeeds). This is not
top-of-the-line hardware by a long shot (Intel(R) Core(TM) i7-4600U CPU
@ 2.10GHz) but I can believe that the other machines are slower or
busier.

Or there might be a completely different explanation ...

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

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Alvaro Herrera 2018-06-29 22:50:55 Re: pgsql: Fix "base" snapshot handling in logical decoding
Previous Message Bruce Momjian 2018-06-29 22:02:07 Re: Tips on committing

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2018-06-29 22:38:36 Re: Explain buffers wrong counter with parallel plans
Previous Message Tom Lane 2018-06-29 22:17:08 Re: Internal error XX000 with enable_partition_pruning=on, pg 11 beta1 on Debian