Re: Consistently use palloc_object() and palloc_array()

David Geier <geidav(dot)pg(at)gmail(dot)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