Re: snapbuild woes
Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
From: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
To: Tom Lane <tgl@sss.pgh.pa.us>, Andres Freund <andres@anarazel.de>
Cc: Noah Misch <noah@leadboat.com>,
Petr Jelinek <petr.jelinek@2ndquadrant.com>, Erik Rijkers <er@xs4all.nl>,
David Steele <david@pgmasters.net>,
PostgreSQL-development <pgsql-hackers@postgresql.org>,
Robert Haas <robertmhaas@gmail.com>, Craig Ringer <craig@2ndquadrant.com>,
pgsql-hackers-owner@postgresql.org
Date: 2017-05-01T22:10:04Z
Lists: pgsql-hackers
On 5/1/17 13:02, Tom Lane wrote: > Andres Freund <andres@anarazel.de> writes: >> On 2017-05-01 12:32:07 -0400, Tom Lane wrote: >>> But quite aside from the question of whether we can afford the cycles, >>> it seems like the wrong approach. IMO the buildfarm is mainly for >>> verifying portability, not for trying to prove that race-like >>> conditions don't exist. In most situations we're going out of our way >>> to ensure reproduceability of tests we add to the buildfarm sequence; >>> but it seems like this is looking for irreproducible results. > >> Yea, I wondered about that upthread as well. But the tests are quite >> useful nonetheless. Wonder about adding them simply as a separate >> target. > > I have no objection to adding more tests as a non-default target. Well, the problem with nondefault targets is that they are hard to find if you don't know them, and then they will rot. Sure, we need a way to distinguish different classes of tests, but lets think about the bigger scheme, too. Ideas welcome. -- Peter Eisentraut http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
Commits
-
Fix thinko introduced in 2bef06d516460 et al.
- d68742562ca4 9.4.13 landed
- 869a5869e5ba 9.5.8 landed
- 32d7480e02ee 9.6.4 landed
- 5af4456a5647 10.0 landed
-
Avoid superfluous work for commits during logical slot creation.
- fa9207c7415c 9.5.8 landed
- bd619fcfe046 9.6.4 landed
- 524dbc14335c 10.0 landed
- 2dca50b764d4 9.4.13 landed
-
Fix race condition leading to hanging logical slot creation.
- b64a68e3680a 9.5.8 landed
- 955a684e0401 10.0 landed
- 79abd23db1e9 9.4.13 landed
- 75784859cda2 9.6.4 landed
-
Don't use on-disk snapshots for exported logical decoding snapshot.
- b6ecf26ccc2b 9.4.12 landed
- 54270d7ebcdc 9.5.7 landed
- 29e8c881dd07 9.6.3 landed
- 56e19d938dd1 10.0 landed
-
Preserve required !catalog tuples while computing initial decoding snapshot.
- 5da64613875d 9.4.12 landed
- 47f896b5c2ec 9.5.7 landed
- 2bef06d51646 10.0 landed
- 28afff347a5d 9.6.3 landed