Re: pgsql: Fix "base" snapshot handling in logical decoding
Alvaro Herrera <alvherre@2ndquadrant.com>
From: Alvaro Herrera <alvherre@2ndquadrant.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-hackers@lists.postgresql.org, 2q-andrew@alvin.alvh.no-ip.org
Date: 2018-06-29T22:50:55Z
Lists: pgsql-hackers
On 2018-Jun-29, Alvaro Herrera wrote: > On 2018-Jun-28, Tom Lane wrote: > > > 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. > > 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. It does fail in the indicated way in CLOBBER_CACHE_RECURSIVELY, but I guess that's expected. It also fails if I reduce the timeout from 60 seconds to 25. 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 ... Another possibility is to examine column 'state' in isolationtester. I thought we only used that timeout for 'waiting' queries, but I see it's not doing that. -- Álvaro Herrera https://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
Commits
-
Reduce cost of test_decoding's new oldest_xmin test
- 7acbb481c808 10.5 landed
- 301b2a1aad77 9.6.10 landed
- eedbbff504e4 9.5.14 landed
- aba2184bed64 11.0 landed
- 8d1c1ca70b01 12.0 landed
-
Fix "base" snapshot handling in logical decoding
- f49a80c481f7 11.0 cited