Re: Failure in commit_ts tap tests
Alvaro Herrera <alvherre@2ndquadrant.com>
From: Alvaro Herrera <alvherre@2ndquadrant.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Andrew Dunstan <andrew.dunstan@2ndquadrant.com>, Pavan Deolasee <pavan.deolasee@gmail.com>, pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2017-01-26T21:46:39Z
Lists: pgsql-hackers
Tom Lane wrote: > Alvaro Herrera <alvherre@2ndquadrant.com> writes: > > It is really quite annoying that the buildfarm doesn't do what stock > > tests do. What about pushing a bit stronger for having these > > optimizations as part of the standard build run, instead of being only > > in the buildfarm client script? > > Huh? It's just a question of "make check" vs "make installcheck". > They each have their uses. The current problem is because the buildfarm uses a different database. See https://postgr.es/m/e6084b89-07a7-7e57-51ee-d7b8fc9ec864@2ndQuadrant.com (When I wrote the para quoted above, I thought this was for performance, but now I realize it's not so. Anyway the point stands that buildfarm does things differently.) -- Álvaro Herrera https://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
Commits
-
Remove test for COMMENT ON DATABASE
- 7fb29ea9c626 9.5.6 landed
- 56b42a334167 9.6.2 landed
- 331f8c311b7b 10.0 landed
-
tests: Use the right Perl operator
- a600ee9e3fcc 10.0 landed