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

From Michael Paquier
Subject Re: creating extension including dependencies
Date
Msg-id CAB7nPqRcbx4gE9d8QpacYRetT49zzGS5Oh=_q6wKGO8Z3W+mEg@mail.gmail.com
Whole thread Raw
In response to Re: creating extension including dependencies  (Petr Jelinek <petr@2ndquadrant.com>)
Responses Re: creating extension including dependencies  (Petr Jelinek <petr@2ndquadrant.com>)
List pgsql-hackers
On Sun, Jul 26, 2015 at 1:01 AM, Petr Jelinek wrote:
> Yes that's what I meant by the change of checking order in the explanation
> above. I did that because I thought code would be more complicated
> otherwise, but apparently I was stupid...

+        In case the extension specifies schema in its control file, the schema
s/schema/<literal>schema</>/

+++ b/src/test/modules/test_extensions/.gitignore
@@ -0,0 +1,3 @@
+# Generated subdirectories
+/results/
+/tmp_check/
test_extensions/.gitignore is missing /log/.

Something also has not been discussed yet: what to do with new_version
and old_version (the options of CreateExtensionStmt)? As of now if
those options are defined they are not passed down to the parent
extensions but shouldn't we raise an error if they are used in
combination with CASCADE? In any case, I think that the behavior
chosen should be documented.
-- 
Michael



pgsql-hackers by date:

Previous
From: Egor Rogov
Date:
Subject: Re: REVOKE [ADMIN OPTION FOR] ROLE
Next
From: Michael Paquier
Date:
Subject: Re: spgist recovery assertion failure