RE: Ability to reference other extensions by schema in extension scripts

From: "Regina Obe" <lr(at)pcorp(dot)us>
To: "'Tom Lane'" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "'Sandro Santilli'" <strk(at)kbt(dot)io>
Cc: "'Gregory Stark \(as CFM\)'" <stark(dot)cfm(at)gmail(dot)com>, <pgsql-hackers(at)lists(dot)postgresql(dot)org>, "'Regina Obe'" <r(at)pcorp(dot)us>
Subject: RE: Ability to reference other extensions by schema in extension scripts
Date: 2023-03-21 14:29:44
Message-ID: 007601d95c01$95744cd0$c05ce670$@pcorp.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2023-03-21 14:52:11 Re: Ability to reference other extensions by schema in extension scripts
Previous Message Tom Lane 2023-03-21 14:01:36 Re: Comment in preptlist.c