Re: Increased SECURITY RISCS from omitting some compikler options when building PG with meson; e.g. -fcf-protection=full

On Wed, 8 Jul 2026 at 12:01, Hans Buschmann <buschmann(at)nidsa(dot)net> wrote:
>
> Most of the flags are compiler-driven, eventually changing with a new version.
>
> I think it is important that these compiler options are DOCUMENTED (in the binary distributions) so that they can be set or verified when self-compiling.

You should be able to grab the compiler and compiler options used to
compile a binary distribution of PostgreSQL from the included
pg_config utility (or pg_config catalog view). Is there information
missing in there that you expected to be available?

> I think the normal user cannot handle all these compiler options, it wants to use the tested and provided standard managed by the developers.

If the normal user cannot handle compiler options, then should they
really be self-compiling PostgreSQL with custom compiler options, for
a platform that already has pre-compiled binary distributions?

Kind regards,

Matthias van de Meent
Databricks (https://www.databricks.com)