| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
| Cc: | Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, Petr Jelinek <petr(at)2ndquadrant(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: creating extension including dependencies |
| Date: | 2015-07-10 13:45:55 |
| Message-ID: | 17377.1436535955@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Michael Paquier <michael(dot)paquier(at)gmail(dot)com> writes:
> On Fri, Jul 10, 2015 at 10:09 PM, Heikki Linnakangas <hlinnaka(at)iki(dot)fi>
>> This seems quite reasonable, but I have to ask: How many extensions are
>> there out there that depend on another extension? Off the top of my head, I
>> can't think of any..
> With transforms there are such dependencies, and there are 3 in contrib/:
> hstore_plperl, hstore_plpython and ltree_plpython.
It's reasonable to expect that such cases will become more common as the
extension community matures. It wasn't something we especially had to
worry about in the initial implementation of extensions, but it seems
totally worthwhile to me to add it now.
FWIW, I agree with using "CASCADE" to signal a request to create required
extension(s) automatically.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2015-07-10 13:52:30 | Re: LANGUAGE sql functions don't use the custom plan logic |
| Previous Message | Fujii Masao | 2015-07-10 13:43:58 | Re: Freeze avoidance of very large table. |