Thread: managing multiple db developers

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.

Thank you,

 - Mark Phillips

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.

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.
>

On Jan 15, 2019, at 10:14 AM, S. Bob <sbob@quadratum-braccas.com> wrote:

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

Thank you for the suggestion. 

My only concern about using pg schemas is the level of separation. Also, I have toyed with create schema but, to my ignorant mind, I don’t see the tables and such in the “dev schema”.

 - Mark

You'll need to augment setting the schema with setting the search_path, you can also set a default search_path for a user

Mark Phillips wrote:
> On Jan 15, 2019, at 10:14 AM, S. Bob <sbob@quadratum-braccas.com> wrote:
> > 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
> 
> Thank you for the suggestion. 
> 
> My only concern about using pg schemas is the level of separation. Also, I have
> toyed with create schema but, to my ignorant mind, I don’t see the tables and such
> in the “dev schema”.

To emulate Oracle's behavior, create user x and his schema with

CREATE ROLE x LOGIN;
CREATE SCHEMA x AUTHORIZATION x;

You don't have to mess with the search_path, because by default
the schema with the same name as the user is the first on the search_path anyway.

There are no "system privileges" to grant.

To be secure, remove the CREATE privilege on the schema "public":

REVOKE CREATE ON SCHEMA public FROM PUBLIC;

Yours,
Laurenz Albe
-- 
Cybertec | https://www.cybertec-postgresql.com