From: | "S(dot) Bob" <sbob(at)quadratum-braccas(dot)com> |
---|---|
To: | pgsql-admin(at)lists(dot)postgresql(dot)org |
Subject: | Re: managing multiple db developers |
Date: | 2019-01-15 18:14:04 |
Message-ID: | 07b5ce6b-3669-a652-e731-b24dbdce60e7@quadratum-braccas.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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(dot)phillips(at)mophilly(dot)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.
>
From | Date | Subject | |
---|---|---|---|
Next Message | Ron | 2019-01-15 18:48:04 | Re: Delete Enhancement Request |
Previous Message | David G. Johnston | 2019-01-15 18:07:36 | Re: managing multiple db developers |