Re: creating extension including dependencies

<div dir="ltr"><br /><div class="gmail_extra"><br /><div class="gmail_quote">On Fri, Jul 10, 2015 at 10:09 PM, Heikki
Linnakangas<span dir="ltr"><<a href="mailto:hlinnaka@iki.fi" target="_blank">hlinnaka@iki.fi</a>></span>
wrote:<br/><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex"><spanclass="">On 07/09/2015 07:05 PM, Petr Jelinek wrote:<br /><blockquote
class="gmail_quote"style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"> On
2015-07-0715:41, Andres Freund wrote:<br /><blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1pxsolid rgb(204,204,204);padding-left:1ex"> On 2015-07-07 22:36:29 +0900, Fujii Masao wrote:<br
/><blockquoteclass="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">On Mon, Jun 15, 2015 at 7:50 AM, Petr Jelinek <<a
href="mailto:petr@2ndquadrant.com"target="_blank">petr@2ndquadrant.com</a>> wrote:<br /><blockquote
class="gmail_quote"style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"> Hi,<br
/><br/> I am getting tired installing manually required extensions manually. I was<br /> wondering if we might want to
addoption to CREATE SEQUENCE that would allow<br /> automatic creation of the extensions required by the extension that
isbeing<br /> installed by the user.<br /></blockquote><br /> I'm wondering how much helpful this feature is. Because,
evenif we can save<br /> some steps for CREATE EXTENSION by using the feature, we still need to<br /> manually find
out,download and install all the extensions that the target<br /> extension depends on. So isn't it better to implement
thetool like yum, i.e.,<br /> which performs all those steps almost automatically, rather than the proposed<br />
feature?Maybe it's outside PostgreSQL core.<br /></blockquote><br /> That doesn't seem to make much sense to me.
Somethinglike yum can't<br /> install everything in all relevant databases. Sure, yum will be used to<br /> install
dependenciesbetween extensions on the filesystem level.<br /><br /> At the minimum I'd like to see that CREATE
EXTENSIONfoo; would install<br /> install extension 'bar' if foo dependended on 'bar' if CASCADE is<br /> specified.
Rightnow we always error out saying that the dependency on<br /> 'bar' is not fullfilled - not particularly helpful.<br
/></blockquote><br/> That's what the proposed patch does (with slightly different syntax but<br /> syntax is something
thatcan be changed easily).<br /></blockquote><br /></span> This seems quite reasonable, but I have to ask: How many
extensionsare there out there that depend on another extension? Off the top of my head, I can't think of any..<span
class=""></span><br/></blockquote></div><br /></div><div class="gmail_extra">With transforms there are such
dependencies,and there are 3 in contrib/: hstore_plperl, hstore_plpython and ltree_plpython.<br />-- <br /><div
class="gmail_signature">Michael<br/></div></div></div>