Re: CI slowdown due to PG_TEST_INITDB_EXTRA_OPTS

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: pgsql-hackers(at)postgresql(dot)org, Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>, Nazir Bilal Yavuz <byavuz81(at)gmail(dot)com>
Subject: Re: CI slowdown due to PG_TEST_INITDB_EXTRA_OPTS
Date: 2026-07-18 18:47:43
Message-ID: 301016.1784400463@sss.pgh.pa.us
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Andres Freund <andres(at)anarazel(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Etsuro Fujita 2026-07-18 18:59:31 Re: use of SPI by postgresImportForeignStatistics
Previous Message Andrey Borodin 2026-07-18 18:29:42 Re: walsummarizer can get stuck when switching timelines