Re: creating extension including dependencies - Mailing list pgsql-hackers

From Tom Lane
Subject Re: creating extension including dependencies
Date
Msg-id 29128.1437488412@sss.pgh.pa.us
Whole thread Raw
In response to Re: creating extension including dependencies  (Petr Jelinek <petr@2ndquadrant.com>)
Responses Re: creating extension including dependencies
List pgsql-hackers
Petr Jelinek <petr@2ndquadrant.com> writes:
> ... My main question is if we are 
> ok with SCHEMA having different behavior with CASCADE vs without 
> CASCADE. I went originally with "no" and added the DEFAULT flag to 
> SCHEMA. If the answer is "yes" then we don't need the flag (in that case 
> CASCADE acts as the flag).

Yeah, I was coming around to that position as well.  Insisting that
SCHEMA throw an error if the extension isn't relocatable makes sense
as long as only one extension is being considered, but once you say
CASCADE it seems like mostly a usability fail.  I think it's probably
OK if with CASCADE, SCHEMA is just "use if needed else ignore".

Obviously we've gotta document all this properly.
        regards, tom lane



pgsql-hackers by date:

Previous
From: Petr Jelinek
Date:
Subject: Re: creating extension including dependencies
Next
From: Robert Haas
Date:
Subject: Re: pgbench stats per script & other stuff