| From: | Greg Sabino Mullane <htamfids(at)gmail(dot)com> |
|---|---|
| To: | Jelte Fennema-Nio <postgres(at)jeltef(dot)nl> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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-08-13 15:37:53 |
| Message-ID: | CAKAnmmJCQ=87NoM_T=8GFCH2PfA3FzxYW8Dpd+5HSEAnLk9yJA@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Aug 11, 2026 at 8:39 AM Jelte Fennema-Nio <postgres(at)jeltef(dot)nl>
wrote:
> I don't think it's that complicated. But I'd be fine with
> PG_TEST_SERVER_POSTGRES_OPTS as well. That has the downside that it
> won't work for actual initdb options, but at least CI doesn't use that
> (for now). Some buildfarm members might though.
>
But they can still use PG_TEST_INITDB_EXTRA_OPTS, right? We are not
replacing the var, just adding a new one, I thought. Probably should
eventually look into caching things for people that use true initdb
options, but I suspect the number of things not handled by the new var will
be very close to zero, so maybe not worth it.
Cheers,
Greg
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bertrand Drouvot | 2026-08-13 15:41:58 | Re: Redesign per-backend statistics |
| Previous Message | Sami Imseih | 2026-08-13 15:35:09 | Re: Disallow outer-level and WHERE-clause aggregates in GRAPH_TABLE |