pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Alvaro Herrera <alvherre@2ndquadrant.com>
To: Andrew Dunstan <andrew.dunstan@2ndquadrant.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Pavan Deolasee <pavan.deolasee@gmail.com>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>
Subject: Re: Failure in commit_ts tap tests
Date: Fri, 27 Jan 2017 09:22:06 -0300
Message-ID: <20170127122206.pj7coisxp2lp6lv6@alvherre.pgsql> (raw)
In-Reply-To: <c1f414f8-9f86-5387-6c8a-91239573f105@2ndQuadrant.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-hackers>

Andrew Dunstan wrote:

> On 01/26/2017 03:50 PM, Alvaro Herrera wrote:

> > 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?
> 
> There is nothing that the buildfarm does that's not a stock test. What
> it does is run the stock tests with USE_MODULE_DB=1 (which you can do
> too). That is something provided for in our Make files. The reason is
> that otherwise we constantly overwrite the regression database. That can
> make it a lot harder to go back after a buildfarm run and find errors.

There is a lot that you *can* do using the stock makefiles, but that
"make check-world" doesn't do.  Why aren't we using USE_MODULE_DB=1 in
"make check-world", is my question.

-- 
Álvaro Herrera                https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services


-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers



view thread (28+ messages)  latest in thread

Message-ID: <20170127122206.pj7coisxp2lp6lv6@alvherre.pgsql>
Permalink:  ../20170127122206.pj7coisxp2lp6lv6@alvherre.pgsql/
Also on:    postgresql.org/message-id/20170127122206.pj7coisxp2lp6lv6@alvherre.pgsql

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-hackers@postgresql.org
  Cc: alvherre@2ndquadrant.com, andrew.dunstan@2ndquadrant.com, tgl@sss.pgh.pa.us, pavan.deolasee@gmail.com
  Subject: Re: Failure in commit_ts tap tests
  In-Reply-To: <20170127122206.pj7coisxp2lp6lv6@alvherre.pgsql>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox