Re: in-catalog Extension Scripts and Control parameters (templates?) - Mailing list pgsql-hackers

From Hitoshi Harada
Subject Re: in-catalog Extension Scripts and Control parameters (templates?)
Date
Msg-id CAP7QgmkAmOpsWFv1_Z=ff2_iU2khxWY1fyNv_ZxkF_qUijo9Dg@mail.gmail.com
Whole thread Raw
In response to Re: in-catalog Extension Scripts and Control parameters (templates?)  (Dimitri Fontaine <dimitri@2ndQuadrant.fr>)
Responses Re: in-catalog Extension Scripts and Control parameters (templates?)
List pgsql-hackers



On Thu, Jun 27, 2013 at 2:49 AM, Dimitri Fontaine <dimitri@2ndquadrant.fr> wrote:
Hi,

Thanks a lot for your review!

Some answers here, new version of the patch with fixes by tuesday.

Hitoshi Harada <umi.tanuki@gmail.com> writes:
> - create template ex2, create extension ex2, alter template ex2 rename to
> ex3, create extension ex3, drop template ex3;
> foo=# drop template for extension ex3 version '1.0';
> ERROR:  cannot drop unrecognized object 3179 16429 0 because other objects
> depend on it

Well, if I'm following, you're trying to remove a non-existing object. I
guess you would prefer a better error message, right?


Right.  unrecognized object x y z doesn't look good.
 
> - 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?
 



--
Hitoshi Harada

pgsql-hackers by date:

Previous
From: Dimitri Fontaine
Date:
Subject: Re: in-catalog Extension Scripts and Control parameters (templates?)
Next
From: Magnus Hagander
Date:
Subject: Re: PostgreSQL 9.3 latest dev snapshot