Hi,
On 2023-02-13 13:54:59 -0500, Tom Lane wrote:
> Bikeshedding a bit ... is "large" the right name? It's not awful but
> I wonder if there is a better one
I did wonder about that too. But didn't come up with something more poignant.
> it seems like this class could eventually include tests that run a long time
> but don't necessarily eat disk space. "resource-intensive" is too long.
I'm not sure we'd want to combine time-intensive and disk-space-intensive test
in the same category. Availability of disk space and cpu cycles don't have to
correlate that well.
lotsadisk, lotsacpu? :)
Greetings,
Andres Freund