RE: Ability to reference other extensions by schema in extension scripts
Regina Obe <lr@pcorp.us>
From: "Regina Obe" <lr@pcorp.us>
To: "'Tom Lane'" <tgl@sss.pgh.pa.us>, "'Sandro Santilli'" <strk@kbt.io>
Cc: "'Gregory Stark \(as CFM\)'" <stark.cfm@gmail.com>, <pgsql-hackers@lists.postgresql.org>, "'Regina Obe'" <r@pcorp.us>
Date: 2023-03-21T14:29:44Z
Lists: pgsql-hackers
> Pushed with some mostly-cosmetic adjustments (in particular I tried to make > the docs and tests neater). > > I did not commit the changes in get_available_versions_for_extension > to add no_relocate as an output column. Those were dead code because you > hadn't done anything to connect them up to an actual output parameter of > pg_available_extension_versions(). While I'm not necessarily averse to > making the no_relocate values visible somehow, I'm not convinced that > pg_available_extension_versions should be the place to do it. ISTM what's > relevant is the no_relocate values of *installed* extensions, not those of > potentially-installable extensions. If we had a view over pg_extension then > that might be a place to add this, but we don't. On the whole it didn't seem > important enough to pursue, so I just left it out. > > regards, tom lane Thanks. Agree with get_available_versions_for_extension, not necessary. Thanks, Regina
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