Re: Ability to reference other extensions by schema in extension scripts
Sandro Santilli <strk@kbt.io>
From: Sandro Santilli <strk@kbt.io>
To: Regina Obe <lr@pcorp.us>
Cc: 'Tom Lane' <tgl@sss.pgh.pa.us>, "'Gregory Stark (as CFM)'" <stark.cfm@gmail.com>, pgsql-hackers@lists.postgresql.org, 'Regina Obe' <r@pcorp.us>
Date: 2023-03-16T10:14:18Z
Lists: pgsql-hackers
On Mon, Mar 13, 2023 at 05:57:57PM -0400, Regina Obe wrote:
>
> Attached is a slightly revised patch to fix the extra whitespace in the
> extend.gml document that Sandro noted to me.
Thanks Regina.
I've tested attached patch (md5 0b652a8271fc7e71ed5f712ac162a0ef)
against current master (hash 4ef1be5a0b676a9f030cc2e4837f4b5650ecb069).
The patch applies cleanly, builds cleanly, regresses cleanly.
I've also run my quick test and I'm satisfied with it:
test=# create extension ext2 cascade;
NOTICE: installing required extension "ext1"
CREATE EXTENSION
test=# select ext2log('h');
ext1: ext2: h
test=# alter extension ext1 set schema n1;
ERROR: cannot SET SCHEMA of extension ext1 because other extensions prevent it
DETAIL: extension ext2 prevents relocation of extension ext1
test=# drop extension ext2;
DROP EXTENSION
test=# alter extension ext1 set schema n1;
ALTER EXTENSION
test=# create extension ext2;
CREATE EXTENSION
test=# select ext2log('h');
ext1: ext2: h
--strk;
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Add @extschema:name@ and no_relocate options to extensions.
- 72a5b1fc8804 16.0 landed
-
pkg-config Requires.private entries should be comma-separated
- 4ef1be5a0b67 16.0 cited
-
Fix logic buglets in pg_dump's flagInhAttrs().
- 128dd9f9eca0 16.0 cited