On 05.12.2012 20:07, Tom Lane wrote:
> Heikki Linnakangas<hlinnakangas@vmware.com> writes:
>> And whether extension control files (or the same information stored in a
>> table or wherever) should be per-database or per cluster - that's *yet*
>> another separate issue. You could argue for either behavior.
>
> I think anyone arguing for the former is confusing an installed
> extension with a not-installed one. Maybe it would help if we adopted
> different terminologies. Perhaps call the control+sql files a "template",
> while using "extension" for the installed entity?
+1 on the naming.
You could still argue that templates should be per-database. It would
make life easier for someone who is database owner but not superuser,
for example, allowing you to install an extension that only affects your
own database (assuming we set up the permissions so that that's
possible, of course).
- Heikki
