From: | Abhijit Menon-Sen <ams(at)2ndQuadrant(dot)com> |
---|---|
To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
Cc: | David Steele <david(at)pgmasters(dot)net>, Robert Haas <robertmhaas(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org, Alexander Korotkov <a(dot)korotkov(at)postgrespro(dot)ru> |
Subject: | Re: dealing with extension dependencies that aren't quite 'e' |
Date: | 2016-04-05 07:38:57 |
Message-ID: | 20160405073857.GA22826@toroid.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
At 2016-04-05 12:33:56 +0530, ams(at)2ndQuadrant(dot)com wrote:
>
> Álvaro: I did document and test the extra types you added, but now
> that I think about it a bit more, it's hard to argue that it's useful
> to have a table, for example, depend on an extension. There's really
> nothing about a table that "doesn't work without" an extension.
I think it makes sense to implement this for triggers and functions. It
may also be useful for indexes and materialised views, which can refer
to functions in an extension (and in future, sequences as well).
It's certainly good to know the grammar would work if we wanted to add
other object types in future, but I think we should leave it at that.
Thoughts?
-- Abhijit
From | Date | Subject | |
---|---|---|---|
Next Message | Craig Ringer | 2016-04-05 07:51:00 | Re: Timeline following for logical slots |
Previous Message | Simon Riggs | 2016-04-05 07:35:53 | Re: Support for N synchronous standby servers - take 2 |