From: Peter Eisentraut <peter.eisentraut@enterprisedb.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
To: pgsql-committers@lists.postgresql.org
Subject: Re: pgsql: Avoid unsatisfied-external-reference errors in static inlines.
Date: Wed, 13 Jul 2022 20:12:23 +0200
Message-ID: <864b47bd-6e82-2d02-070d-ae5076d8c4c1@enterprisedb.com> (raw)
In-Reply-To: <E1oBgIW-002ehP-VJ@gemulon.postgresql.org>
References: <E1oBgIW-002ehP-VJ@gemulon.postgresql.org>
On 13.07.22 19:37, Tom Lane wrote:
> Avoid unsatisfied-external-reference errors in static inlines.
>
> Commit 9c727360b neglected the lesson we've learned before:
> protect references to backend global variables with #ifndef FRONTEND.
What platforms did this fail on? How can one observe the failure locally?
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-committers@postgresql.org
Cc: peter.eisentraut@enterprisedb.com, tgl@sss.pgh.pa.us
Subject: Re: pgsql: Avoid unsatisfied-external-reference errors in static inlines.
In-Reply-To: <864b47bd-6e82-2d02-070d-ae5076d8c4c1@enterprisedb.com>
References: <E1oBgIW-002ehP-VJ@gemulon.postgresql.org> <864b47bd-6e82-2d02-070d-ae5076d8c4c1@enterprisedb.com>
* 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