Re: pgsql: Avoid unsatisfied-external-reference errors in static inlines.

From: Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: Re: pgsql: Avoid unsatisfied-external-reference errors in static inlines.
Date: 2022-07-13 18:12:23
Message-ID: 864b47bd-6e82-2d02-070d-ae5076d8c4c1@enterprisedb.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-committers

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?

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2022-07-13 18:24:49 Re: pgsql: Avoid unsatisfied-external-reference errors in static inlines.
Previous Message Tom Lane 2022-07-13 17:37:18 pgsql: Avoid unsatisfied-external-reference errors in static inlines.