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

From Robert Haas
Subject Re: creating extension including dependencies
Date
Msg-id CA+TgmoYb5FOAp8HfNbL+3T7aM75=TRkPTkkB6kSHUx3q3PjXLw@mail.gmail.com
Whole thread Raw
In response to Re: creating extension including dependencies  (Michael Paquier <michael.paquier@gmail.com>)
Responses Re: creating extension including dependencies  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Mon, Jul 20, 2015 at 10:29 PM, Michael Paquier
<michael.paquier@gmail.com> wrote:> In > short I would give up on the
DEFAULT SCHEMA business, and
> add a new flag in the control file to decide if a given extension
> passes down the schema name of its child when created in cascade,
> default being true for the potential issues with search_path not
> pointing to public.

Well, so far, it seems like this decision is something where different
DBAs might have different policies.  If you put the flag in the
control file, you're saying it is the extension developer's decision,
which may not be best.

Maybe I'm confused.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: Fillfactor for GIN indexes
Next
From: Alexander Korotkov
Date:
Subject: Re: Fillfactor for GIN indexes