|From:||Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>|
|To:||"Regina Obe" <lr(at)pcorp(dot)us>|
|Cc:||"'Sandro Santilli'" <strk(at)kbt(dot)io>, "'Gregory Stark \(as CFM\)'" <stark(dot)cfm(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org|
|Subject:||Re: Ability to reference other extensions by schema in extension scripts|
|Views:||Raw Message | Whole Thread | Download mbox | Resend email|
"Regina Obe" <lr(at)pcorp(dot)us> writes:
>> 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.
> Thanks. Agree with get_available_versions_for_extension, not necessary.
If we did feel like doing something about this, on reflection I think
the thing to do would be to add no_relocate as an actual column in
pg_extension, probably of type "oid". Then we could modify the
SET SCHEMA code to check that instead of parsing the extension control
files. That'd be a little cleaner, but I can't say that I'm hugely
excited about it.
regards, tom lane
|Next Message||Merlin Moncure||2023-03-21 14:57:18||Re: Request for comment on setting binary format output per session|
|Previous Message||Regina Obe||2023-03-21 14:29:44||RE: Ability to reference other extensions by schema in extension scripts|