pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: David Geier <geidav.pg@gmail.com>
Cc: Michael Paquier <michael@paquier.xyz>
Cc: Thomas Munro <thomas.munro@gmail.com>
Cc: Chao Li <li.evan.chao@gmail.com>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>
Subject: Re: Consistently use palloc_object() and palloc_array()
Date: Thu, 11 Dec 2025 10:32:26 -0500
Message-ID: <830615.1765467146@sss.pgh.pa.us> (raw)
In-Reply-To: <a5c633b1-641e-43bd-b89d-984df1002f7e@gmail.com>
References: <ad0748d4-3080-436e-b0bc-ac8f86a3466a@gmail.com>
	<ED821EDD-6A1B-45B8-9005-31BCFFCB5A48@gmail.com>
	<a29b0cd9-576f-486f-ba45-5139ee33adcf@gmail.com>
	<524587.1764365323@sss.pgh.pa.us>
	<1e7f0c17-a965-4d5b-ad88-b435a4d97490@gmail.com>
	<CA+hUKGL+hiMRrAOqop1wmfpqTLg3GdyAJmO6KH6Dz3FjQvGN+w@mail.gmail.com>
	<143d3184-b575-49bd-8bc1-f37f45f010cc@gmail.com>
	<aS-F6LkeDBEly9nz@paquier.xyz>
	<534126.1764722446@sss.pgh.pa.us>
	<4ab4a12b-49e9-4ebf-9055-225c8055fed0@gmail.com>
	<aTKMtSMTh4eiSGMr@paquier.xyz>
	<accd2714-19ea-43a6-b4ea-29ae5416431c@gmail.com>
	<1433178.1764946037@sss.pgh.pa.us>
	<a5c633b1-641e-43bd-b89d-984df1002f7e@gmail.com>

David Geier <geidav.pg@gmail.com> writes:
> Do we know what code each build animal actually has enabled?

Of course.  The configuration is reported in the logs of every
buildfarm run.  For instance, in the most recent run at this
moment,

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=caiman&dt=2025-12-11%2015%3A00%3A05

we can see

  $ ./configure --enable-cassert --enable-debug --enable-nls --with-perl \
        --with-python --with-tcl --with-gssapi --with-openssl --with-ldap \
        --with-libxml --with-libxslt --with-pam --with-selinux \
        --with-systemd --with-liburing --with-libcurl --with-libnuma \
        --with-lz4 --with-zstd --prefix=/repos/client-code-REL_20/HEAD/inst \
        --with-pgport=5678 --cache-file=/repos/client-code-REL_20/accache-caiman/config-HEAD.cache

and you can drill down to the "configure" step if you want more
detail.

> Do build animal owners try to enable as much code as possible, or is
> this completely up to what the owner happened to do when setting up the
> build animal?

It's the owner's choice.  The buildfarm client's sample config file
has a list of suggested options, and I wouldn't be too surprised
if a lot of people just left that list alone.  I think the ones
paying closer attention probably try to enable as much as they can.

			regards, tom lane





view thread (29+ messages)

Message-ID: <830615.1765467146@sss.pgh.pa.us>
Permalink:  ../830615.1765467146@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/830615.1765467146@sss.pgh.pa.us

 · 

reply
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, geidav.pg@gmail.com, michael@paquier.xyz, thomas.munro@gmail.com, li.evan.chao@gmail.com
  Subject: Re: Consistently use palloc_object() and palloc_array()
  In-Reply-To: <830615.1765467146@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