Re: Extension security improvement: Add support for extensions with an owned schema

From: Artem Gavrilov <artem(dot)gavrilov(at)percona(dot)com>
To: Jelte Fennema-Nio <me(at)jeltef(dot)nl>
Cc: Tomas Vondra <tomas(at)vondra(dot)me>, "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, 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: 2025-07-23 17:12:42
Message-ID: CAFPkQKzALOTTBrhj2qDHwVxZQyjF5Xg_P9M=Tn_Dcm3vr=xdTA@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hello Jelte,

I reviewed your patch. Overall it looks good, I didn't find any problems
with code. Documentation is in place and clear.

Initial Run
===========
The patch applies cleanly to HEAD (196063d6761). All tests successfully
pass.

Comments
===========
1) I noticed that pg_dump changes weren't covered with tests.

2) I assume these error messages may be confusing, especially first one:

> -- Fails for an already existing schema to be provided
> CREATE EXTENSION test_ext_owned_schema SCHEMA test_ext_owned_schema;
> ERROR: schema "test_ext_owned_schema" already exists
> -- Fails because a different schema is set in control file
> CREATE EXTENSION test_ext_owned_schema SCHEMA test_schema;
> ERROR: extension "test_ext_owned_schema" must be installed in schema
> "test_ext_owned_schema"

In both cases it's not clear that the extension requires schema ownership.
Can hint messages be added there?

--

Artem Gavrilov

Senior Software Engineer, Percona

artem(dot)gavrilov(at)percona(dot)com
percona.com <http://www.percona.com>

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Álvaro Herrera 2025-07-23 17:26:28 Re: trivial grammar refactor
Previous Message Jacob Champion 2025-07-23 17:11:07 Re: Support getrandom() for pg_strong_random() source