Re: in-catalog Extension Scripts and Control parameters (templates?)

From: Dimitri Fontaine <dimitri(at)2ndQuadrant(dot)fr>
To: Hitoshi Harada <umi(dot)tanuki(at)gmail(dot)com>
Cc: Jaime Casanova <jaime(at)2ndquadrant(dot)com>, Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Stephen Frost <sfrost(at)snowman(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: in-catalog Extension Scripts and Control parameters (templates?)
Date: 2013-06-27 11:34:44
Message-ID: m2obaryegb.fsf@2ndQuadrant.fr
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hitoshi Harada <umi(dot)tanuki(at)gmail(dot)com> writes:
>> > - a template that is created in another template script does not appear
>> to
>> > depend on the parent template.
>>
>> I don't think that should be automatically the case, even if I admit I
>> didn't think about that case.
>>
> Really? My understanding is everything that is created under extension
> depends on the extension, which depends on the template. Why only template
> is exception?

Oh sorry, I understood you meant at CREATE TEMPLATE FOR EXTENSION time
rather than at CREATE EXTENSION time, and that you were refering to
dependency as in the "require" control parameter.

The pg_depend entry against the extension should be there, will fix.

Regards,
--
Dimitri Fontaine
http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message MauMau 2013-06-27 11:53:24 [9.3 doc fix] ECPG VAR command does not describe the actual specification
Previous Message Marko Kreen 2013-06-27 11:29:22 Re: MD5 aggregate