Re: pg_upgrade fails when extension_control_path is used

From: Matheus Alcantara <matheusssilv97(at)gmail(dot)com>
To: "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-09 20:49:35
Message-ID: 16329a4b-2cbb-4e17-bf6e-85d880f9d493@gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.

--
Matheus Alcantara
EDB: https://www.enterprisedb.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Nathan Bossart 2026-03-09 21:04:05 Re: Add starelid, attnum to pg_stats and leverage this in pg_dump
Previous Message Peter Geoghegan 2026-03-09 20:14:49 Re: Correcting freeze conflict horizon calculation