Re: Add resource intensiveness as a reason to not running tests by default

From: Daniel Gustafsson <daniel(at)yesql(dot)se>
To: Nazir Bilal Yavuz <byavuz81(at)gmail(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Add resource intensiveness as a reason to not running tests by default
Date: 2023-09-07 11:24:16
Message-ID: 1F258553-4987-468D-B2A3-F7AFCD7697B4@yesql.se
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On 7 Sep 2023, at 13:09, Nazir Bilal Yavuz <byavuz81(at)gmail(dot)com> wrote:

> With f47ed79cc8, the test suite doesn't run 'wal_consistency_checking'
> as default because it is resource intensive; but regress docs doesn't
> state resource intensiveness as a reason for not running tests by
> default. So, I created a patch for updating the docs.

Agreed, the current wording lacks the mention of skipping tests due to high
resource usage. Patch looks good from a quick skim, I'll backpatch it down to
15 which is where PG_TEST_EXTRA was first used in this capacity.

--
Daniel Gustafsson

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Thomas Munro 2023-09-07 11:30:15 Re: Cutting support for OpenSSL 1.0.1 and 1.0.2 in 17~?
Previous Message Nazir Bilal Yavuz 2023-09-07 11:09:35 Add resource intensiveness as a reason to not running tests by default