Andres Freund <and...@anarazel.de> writes: > On 2023-02-13 13:54:59 -0500, Tom Lane wrote: >> 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. Yeah, I was thinking along the same lines. > lotsadisk, lotsacpu? :) bigdisk, bigcpu? regards, tom lane