Re: pgsql: Fix "base" snapshot handling in logical decoding - Mailing list pgsql-committers

From Tom Lane
Subject Re: pgsql: Fix "base" snapshot handling in logical decoding
Date
Msg-id 26020.1530244390@sss.pgh.pa.us
Whole thread Raw
In response to pgsql: Fix "base" snapshot handling in logical decoding  (Alvaro Herrera <alvherre@alvh.no-ip.org>)
Responses Re: pgsql: Fix "base" snapshot handling in logical decoding  (Alvaro Herrera <alvherre@2ndquadrant.com>)
List pgsql-committers
Alvaro Herrera <alvherre@alvh.no-ip.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.

friarbird's error output doesn't seem to be getting captured by the
buildfarm script, but what I see is

***************
*** 16,21 ****
--- 16,22 ----

  step s1_commit: COMMIT;
  step s0_vacuum: VACUUM FULL;
+ ERROR:  canceling statement due to user request
  step s0_get_changes: SELECT data FROM pg_logical_slot_get_changes('isolation_s
lot', NULL, NULL, 'include-xids', '0', 'skip-empty-xacts', '1');
  data

which looks like it might just be a timeout problem.

            regards, tom lane


pgsql-committers by date:

Previous
From: Michael Paquier
Date:
Subject: pgsql: Make capitalization of term "OpenSSL" more consistent
Next
From: David Rowley
Date:
Subject: Re: pgsql: Clarify use of temporary tables within partition trees