pgsql: ci: Get build/test concurrency from environment

From: Andres Freund <andres(at)anarazel(dot)de>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: ci: Get build/test concurrency from environment
Date: 2026-11-06 02:50:25
Message-ID: E1xPA25-00000000P86-1gha@gemulon.postgresql.org
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-committers

ci: Get build/test concurrency from environment

Previously we hardcoded the amount of concurrency in the CI definition. This
practice IIRC originated from a) using make, where the concurrency is not
sourced from the current system b) early cirrus-ci macos runners, which slowed
down a lot with full concurrency.

Hardcoding the concurrency is problematic as e.g. private repositories have
lower concurrency and larger github runners have more cores.

For most of the jobs we can rely on just using meson's and ninja's logic for
getting the current core count. For the autoconf build we can use the nproc
helper.

To make this at least somewhat understandable, I extended the existing sysinfo
step to show the number of cores (and made it a bit easier to understand the
information already printed).

This commit is backpatched to 19 to keep CI between master and 19 the
same. Soon we'll backpatch CI support to regain coverage with lost with
cirrus-ci's shutdown.

Author: Andres Freund <andres(at)anarazel(dot)de>
Co-authored-by: Nazir Bilal Yavuz <byavuz81(at)gmail(dot)com>
Discussion: https://postgr.es/m/a2ejn7lfqolutzz7kozalbhy3bixdrujb4buc3pgbtlk4am2ba@wbv6v7riia33
Discussion: https://postgr.es/m/CAN55FZ1BcWBsWgCCk2GQkYN6tzDxCw2hVK2m3qeiwaNXUnjLVg@mail.gmail.com
Backpatch-through: 19

Branch
------
REL_19_STABLE

Details
-------
https://git.postgresql.org/pg/commitdiff/805451142de5804db7c44603755ff6354825609f

Modified Files
--------------
.github/workflows/pg-ci.yml | 43 ++++++++++++++++++++++++++-----------------
1 file changed, 26 insertions(+), 17 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2026-11-06 03:07:27 Re: pgsql: Handle numeric overflow in numeric_minmax_multi_ops
Previous Message Michael Paquier 2026-11-06 01:46:17 pgsql: Revert "Fix use-after-free in COPY (ON_ERROR)"