| From: | Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com> |
|---|---|
| To: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | TAP tests - installcheck vs check |
| Date: | 2017-04-23 22:29:04 |
| Message-ID: | c8089bcd-e5f9-3a05-136a-f183207bb5f9@2ndQuadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
AFAICT, unlike the pg_regress checks, which in the installcheck case run
against a running instance of postgres, for TAP tests the only
difference is that that for the check case a temp install is done,
possibly with some extra contrib modules. Is that correct? If is is, why
aren't we providing an installcheck target for tests like recover. In at
least one case (buildfarmn jacana) installs are quite expensive (2 or 3
minutes) and if they are pointless as seems to be the case here why
can't we just avoid them?
cheers
andrew
--
Andrew Dunstan https://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Munro | 2017-04-23 22:34:44 | Re: [COMMITTERS] pgsql: Replication lag tracking for walsenders |
| Previous Message | Petr Jelinek | 2017-04-23 21:17:58 | Re: valgrind error in subscription code |