From: suresh neravati <suresh.neravati@yahoo.com>
To: Mark Phillips <mark.phillips@mophilly.com>
To: David G. Johnston <david.g.johnston@gmail.com>
Cc: pgsql-admin@lists.postgresql.org <pgsql-admin@lists.postgresql.org>
Subject: Re: managing multiple db developers
Date: Tue, 15 Jan 2019 20:16:18 +0000 (UTC)
Message-ID: <1504617051.14816.1547583378151@mail.yahoo.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>
You can create individual database for each developer. That works as a cluster, but you can specify smaller memory numbers for each developer.
On Tuesday, January 15, 2019, 10:08:05 AM PST, David G. Johnston <david.g.johnston@gmail.com> 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: suresh.neravati@yahoo.com, mark.phillips@mophilly.com, david.g.johnston@gmail.com, pgsql-admin@lists.postgresql.org
Subject: Re: managing multiple db developers
In-Reply-To: <1504617051.14816.1547583378151@mail.yahoo.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