| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Petr Jelinek <petr(at)2ndquadrant(dot)com>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: creating extension including dependencies |
| Date: | 2015-09-16 22:46:10 |
| Message-ID: | 20150916224610.GU88970@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Andres Freund wrote:
> > @@ -91,8 +92,38 @@ CREATE EXTENSION [ IF NOT EXISTS ] <replaceable class="parameter">extension_name
> > The name of the schema in which to install the extension's
> > objects, given that the extension allows its contents to be
> > relocated. The named schema must already exist.
> > - If not specified, and the extension's control file does not specify a
> > - schema either, the current default object creation schema is used.
> > + If not specified, and the extension control file does not define
> > + <literal>schema</> either, the current default object creation
> > + schema is used.
> > + </para>
>
> Imo still a spurious change.
I think some more work is needed in this file -- ISTM the rules used to
determine the creation schema under CASCADE should not be placed within
the SCHEMA clause explanation.
--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2015-09-16 22:48:18 | Re: creating extension including dependencies |
| Previous Message | Andres Freund | 2015-09-16 22:42:09 | Re: Improving test coverage of extensions with pg_dump |