From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andres Freund <andres@anarazel.de>
Cc: pgsql-hackers@postgresql.org, Peter Eisentraut <peter.eisentraut@enterprisedb.com>
Cc: Nazir Bilal Yavuz <byavuz81@gmail.com>
Subject: Re: CI slowdown due to PG_TEST_INITDB_EXTRA_OPTS
Date: Sat, 18 Jul 2026 14:47:43 -0400
Message-ID: <301016.1784400463@sss.pgh.pa.us> (raw)
In-Reply-To: <r75blb6gfaqplk7jvwdjz5sjxryl73y2t2ih2lja6ptwb6ujbh@k3jyvsdd6way>
References: <r75blb6gfaqplk7jvwdjz5sjxryl73y2t2ih2lja6ptwb6ujbh@k3jyvsdd6way>
Andres Freund <andres@anarazel.de> writes:
> I was once more wondering why CI is so slow. While thinking about what
> measurements to take, I think I figured out a major source:
> Many of the jobs use PG_TEST_INITDB_EXTRA_OPTS. Unfortunately, using that
> turns out to disable the initdb template mechanism:
> ...
> Any better ideas?
It looks like any one job mostly uses the same value of
PG_TEST_INITDB_EXTRA_OPTS. Could we record what was used to set up
the template, and allow using it if that matches?
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: tgl@sss.pgh.pa.us, andres@anarazel.de, peter.eisentraut@enterprisedb.com, byavuz81@gmail.com
Subject: Re: CI slowdown due to PG_TEST_INITDB_EXTRA_OPTS
In-Reply-To: <301016.1784400463@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox