| From: | Jelte Fennema-Nio <me(at)jeltef(dot)nl> |
|---|---|
| To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
| Cc: | Jeff Davis <pgsql(at)j-davis(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Extension security improvement: Add support for extensions with an owned schema |
| Date: | 2024-06-20 11:18:03 |
| Message-ID: | CAGECzQTOJrnnJkmMe9nems0jouiKUbFcEb1rb9kE_svsAZiGQg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, 19 Jun 2024 at 17:22, David G. Johnston
<david(dot)g(dot)johnston(at)gmail(dot)com> wrote:
>
> On Wed, Jun 19, 2024 at 8:19 AM Jelte Fennema-Nio <me(at)jeltef(dot)nl> wrote:
>
>>
>> Because part of it would
>> only be relevant once we support upgrading from PG18. So for now the
>> upgrade_code I haven't actually run.
>
>
> Does it apply against v16? If so, branch off there, apply it, then upgrade from the v16 branch to master.
I realized it's possible to do an "upgrade" with pg_upgrade from v17
to v17. So I was able to test both the pre and post PG18 upgrade logic
manually by changing the version in this line:
if (fout->remoteVersion >= 180000)
As expected the new pg_upgrade code was severely broken. Attached is a
new patch where the pg_upgrade code now actually works.
| Attachment | Content-Type | Size |
|---|---|---|
| v3-0001-Add-support-for-extensions-with-an-owned-schema.patch | application/octet-stream | 30.8 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ranier Vilela | 2024-06-20 11:32:05 | Re: confusing valgrind report about tuplestore+wrapper_handler (?) on 32-bit arm |
| Previous Message | Hannu Krosing | 2024-06-20 11:08:57 | Re: What is a typical precision of gettimeofday()? |