Re: Adjust pg_regress output for new long test names

From: Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>
To: Noah Misch <noah(at)leadboat(dot)com>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Adjust pg_regress output for new long test names
Date: 2021-06-09 17:36:06
Message-ID: d70c8ee9-aa1b-0141-58e1-5ff359241f29@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 09.06.21 04:51, Noah Misch wrote:
> On Wed, Jun 09, 2021 at 01:57:45PM +1200, Thomas Munro wrote:
>> test deadlock-simple ... ok 20 ms
>> test deadlock-hard ... ok 10624 ms
>> test deadlock-soft ... ok 147 ms
>> test deadlock-soft-2 ... ok 5154 ms
>> test deadlock-parallel ... ok 132 ms
>> test detach-partition-concurrently-1 ... ok 553 ms
>> test detach-partition-concurrently-2 ... ok 234 ms
>> test detach-partition-concurrently-3 ... ok 2389 ms
>> test detach-partition-concurrently-4 ... ok 1876 ms
>> Make the test output visually consistent, as previously done by commit
>> 14378245.
> Not bad, but I would instead shorten the names to detach-[1234] or
> detach-partition-[1234]. The marginal value of the second word is low, and
> the third word helps even less.

DETACH CONCURRENTLY is a separate feature from plain DETACH.

But "partition" is surely redundant here.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2021-06-09 17:37:01 Re: Adjust pg_regress output for new long test names
Previous Message Tom Lane 2021-06-09 17:25:59 Re: Add PortalDrop in exec_execute_message