Heikki Linnakangas <hlinnakangas@vmware.com> writes:
> Right. I think Jeff was thinking of a catalog representation for extensions
> that haven't been installed yet, but are available in the system and could
> be installed with CREATE EXTENSION foo. I wouldn't mind having a catalog
> like that. Even without any of this extension template stuff, it would be
> handy to have a view that lists all the extensions available in the
> filesystem.
http://www.postgresql.org/docs/9.1/static/view-pg-available-extensions.html
http://www.postgresql.org/docs/9.1/static/view-pg-available-extension-versions.html
> There should be no difference between file-based extensions and
> catalog-based extensions. It's just two different ways to install the same
> extension. The extension author doesn't need to care about that, it's the
> DBA that decides which method to use to install it.
Agreed.
> I'm going to object loudly to any proposal that doesn't meet that criteria.
Please be kind enough to poin me where my current patch is drifting away
from that criteria. What you're proposing here is what I think I have
been implementing.
Regards,
--
Dimitri Fontaine
http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support