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>
Cc: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: Re: pgsql: Avoid unsatisfied-external-reference errors in static inlines.
Date: 2022-07-14 10:05:13
Message-ID: 1b09ac8a-5906-3a52-3763-44a9b2115805@enterprisedb.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-committers

On 13.07.22 20:24, Tom Lane wrote:
> Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> writes:
>> What platforms did this fail on? How can one observe the failure locally?
>
> wrasse at least:
>
> https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=wrasse&dt=2022-07-13%2014%3A49%3A17
>
> I think possibly you could duplicate the problem with gcc
> by using -fkeep-inline-functions, but I've not tried.

Confirmed, -fkeep-inline-functions will catch it. Good to know.

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Thomas Munro 2022-07-14 12:00:34 pgsql: Block signals while allocating DSM memory.
Previous Message John Naylor 2022-07-14 02:39:27 pgsql: Correct some uses of e.g. and i.e. in message strings and docume