| From: | Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com> |
|---|---|
| To: | Craig Ringer <craig(dot)ringer(at)2ndquadrant(dot)com>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Robert Haas <robertmhaas(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Subject: | Re: TAP tests take a long time |
| Date: | 2017-04-12 19:31:10 |
| Message-ID: | e917b1d7-56af-c5ab-3a2a-b52bbadc19b2@2ndQuadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 04/12/2017 08:40 AM, Andrew Dunstan wrote:
>
> On 04/12/2017 01:27 AM, Craig Ringer wrote:
>> BTW, I suggest adding --timer to our default PROVE_FLAGS, so we can
>> collect more data from the buildfarm on what takes a while. Sample
>> output:
>>
>
> I'll add that to the commandline the buildfarm uses in the upcoming release.
>
See
<https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=nightjar&dt=2017-04-12%2013%3A54%3A22>
One thing I noticed was this
[10:02:40] t/001_basic.pl ......... ok 320 ms
[10:02:59] t/002_pg_dump.pl ....... ok 19441 ms
[10:03:47] t/010_dump_connstr.pl .. ok 47430 ms
Why does the last test set take 47s?
cheers
andrew
--
Andrew Dunstan https://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2017-04-12 19:35:28 | Re: Vacuum: allow usage of more than 1GB of work mem |
| Previous Message | Stephen Frost | 2017-04-12 19:29:30 | Re: pg_dump emits ALTER TABLE ONLY partitioned_table |