From: S. Bob <sbob@quadratum-braccas.com>
To: pgsql-admin@lists.postgresql.org
Subject: Re: managing multiple db developers
Date: Tue, 15 Jan 2019 11:14:04 -0700
Message-ID: <07b5ce6b-3669-a652-e731-b24dbdce60e7@quadratum-braccas.com> (raw)
In-Reply-To: <CAKFQuwZm4+AjjMateQ7-o24ogjfmgFYA2mt9qJtOtSt81LPmeA@mail.gmail.com>
References: <B9B624EE-1106-4FDA-8931-9346979F57EE@mophilly.com>
<CAKFQuwZm4+AjjMateQ7-o24ogjfmgFYA2mt9qJtOtSt81LPmeA@mail.gmail.com>
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.
>
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: sbob@quadratum-braccas.com, pgsql-admin@lists.postgresql.org
Subject: Re: managing multiple db developers
In-Reply-To: <07b5ce6b-3669-a652-e731-b24dbdce60e7@quadratum-braccas.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox