public inbox for [email protected]  

help / color / mirror / Atom feed

From: Matthias van de Meent <[email protected]>
To: Hans Buschmann <[email protected]>
Cc: Peter Eisentraut <[email protected]>
Cc: [email protected] <[email protected]>
Subject: Re: Increased SECURITY RISCS from omitting some compikler options when building PG with meson; e.g. -fcf-protection=full
Date: Wed, 8 Jul 2026 12:57:00 +0200
Message-ID: <CAEze2Wh+ZzS=CpOa1HA2uJd2tqsJcqUyz=PamvNGaJBtgmQyXw@mail.gmail.com> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<[email protected]>
	<[email protected]>

On Wed, 8 Jul 2026 at 12:01, Hans Buschmann <[email protected]> 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)

view thread (6+ messages)  latest in thread

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: [email protected]
  Cc: [email protected], [email protected], [email protected]
  Subject: Re: Increased SECURITY RISCS from omitting some compikler options when building PG with meson; e.g. -fcf-protection=full
  In-Reply-To: <CAEze2Wh+ZzS=CpOa1HA2uJd2tqsJcqUyz=PamvNGaJBtgmQyXw@mail.gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox