Re: managing multiple db developers - Mailing list pgsql-admin

From S. Bob
Subject Re: managing multiple db developers
Date
Msg-id 07b5ce6b-3669-a652-e731-b24dbdce60e7@quadratum-braccas.com
Whole thread Raw
In response to Re: managing multiple db developers  ("David G. Johnston" <david.g.johnston@gmail.com>)
Responses Re: managing multiple db developers  (Mark Phillips <mark.phillips@mophilly.com>)
List pgsql-admin
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
instanceof our own for experiments, including modifying stored procedures and such, without the risk of negative impact
onother 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.
>


pgsql-admin by date:

Previous
From: "David G. Johnston"
Date:
Subject: Re: managing multiple db developers
Next
From: Ron
Date:
Subject: Re: Delete Enhancement Request