From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Bryn Llewellyn <bryn(at)yugabyte(dot)com> |
Cc: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, pgsql-general list <pgsql-general(at)lists(dot)postgresql(dot)org> |
Subject: | Re: "create function... depends on extension..." not supported. Why? |
Date: | 2022-04-27 01:31:51 |
Message-ID: | 294570.1651023111@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Bryn Llewellyn <bryn(at)yugabyte(dot)com> writes:
> The discussion has diverging threads and very many turns. I think that I managed to skim through the entire tree. As I read it, the discussion was entirely about the semantics of the proposed dependency of a function (or procedure) upon an extension. The idea to establish such a dependency using “alter function” came up quite early in the discussion. It seems that establishing it at “create function” time was never considered.
Probably not. Just for the record, it's not true that CREATE and ALTER
always have the same set of options. An obvious counterexample is that
you can't set the owner to someone different from yourself during CREATE.
There may be others.
I suppose that "DEPENDS ON EXTENSION" was modeled after the commands
to control extension membership, which likewise exist only in ALTER
form because CREATE's behavior for that is hard-wired. If you wanted
to hand-wave a lot, you could maybe claim that ownership and extension
membership/dependency are similar kinds of relationships and so it
makes sense that the command structures for manipulating them are
similar. But TBH that would probably be reverse-engineering an
explanation. I think that "we didn't bother" is more nearly the
situation.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2022-04-27 03:11:46 | Re: Fresh eyeballs needed: input into error [FIXED] |
Previous Message | Bryn Llewellyn | 2022-04-27 01:20:46 | Re: "create function... depends on extension..." not supported. Why? |