Re: pg_upgrade fails when extension_control_path is used

From: Peter Eisentraut <peter(at)eisentraut(dot)org>
To: Matheus Alcantara <matheusssilv97(at)gmail(dot)com>, "Jonathan Gonzalez V(dot)" <jonathan(dot)abdiel(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_upgrade fails when extension_control_path is used
Date: 2026-03-16 10:57:14
Message-ID: e342c004-287d-4275-a912-b9dcdfe9f6d7@eisentraut.org
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 09.03.26 21:49, Matheus Alcantara wrote:
> On 06/03/26 09:10, Jonathan Gonzalez V. wrote:
>> Hello!
>>
>>>   that the code comment on function.c can be
>>> similar to what we have on load_external_function():
>>>
>>>    /*
>>>    * For extensions with hardcoded '$libdir/' library names, we
>>>    * strip the prefix to allow the library search path to be used.
>>>    */
>>>
>>>>
>> I'm attaching a v3 with an improved messages
>>
>> Also updated the reviewers list on the message
>>
>
> Thanks for updating the patch, it looks good to me and fix the described
> issue.

committed

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Kapila 2026-03-16 11:10:01 Re: Report bytes and transactions actually sent downtream
Previous Message vignesh C 2026-03-16 10:56:00 Re: Skipping schema changes in publication