Re: [HACKERS] Failure in commit_ts tap tests - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: [HACKERS] Failure in commit_ts tap tests
Date
Msg-id 20170126214639.2ukhwucaelhdzetg@alvherre.pgsql
Whole thread Raw
In response to Re: [HACKERS] Failure in commit_ts tap tests  (Tom Lane <tgl@sss.pgh.pa.us>)
List 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



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [HACKERS] Failure in commit_ts tap tests
Next
From: Tom Lane
Date:
Subject: Re: [HACKERS] safer node casting