Subject: Re: managing multiple db developers
To: pgsql-admin@lists.postgresql.org
References: <B9B624EE-1106-4FDA-8931-9346979F57EE@mophilly.com>
 <CAKFQuwZm4+AjjMateQ7-o24ogjfmgFYA2mt9qJtOtSt81LPmeA@mail.gmail.com>
From: "S. Bob" <sbob@quadratum-braccas.com>
Message-ID: <07b5ce6b-3669-a652-e731-b24dbdce60e7@quadratum-braccas.com>
Date: Tue, 15 Jan 2019 11:14:04 -0700
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101
 Thunderbird/60.4.0
MIME-Version: 1.0
In-Reply-To: 
 <CAKFQuwZm4+AjjMateQ7-o24ogjfmgFYA2mt9qJtOtSt81LPmeA@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Precedence: bulk

PostgreSQL supports schema's as well, a schema in PostgreSQL is a simple 
namespace, which is a different concept from Oracle but you can 
accomplish the same thing with a schema, in particular via the "CREATE 
SCHEMA AUTHORIZATION" approach


https://www.postgresql.org/docs/11/sql-createschema.html


On 1/15/19 11:07 AM, David G. Johnston wrote:
> On Tue, Jan 15, 2019 at 10:44 AM Mark Phillips
> <mark.phillips@mophilly.com> wrote:
>> When I worked for an Oracle shop, the dba set up individual “schemas” for each developer. That allowed us a database instance of our own for experiments, including modifying stored procedures and such, without the risk of negative impact on other developers or modifying the stable dev-test and QA databases.
>>
>> I am wondering how to accomplish a similar arrangement in an postgres cluster.
> I recommend leveraging the fact that PostgreSQL lacks per-instance
> licensing fees and have each developer run (more or less)
>
> apt-get install postgresql
>
> on their personal development virtual machine
>
> David J.
>