| From: | suresh neravati <suresh(dot)neravati(at)yahoo(dot)com> |
|---|---|
| To: | Mark Phillips <mark(dot)phillips(at)mophilly(dot)com>, "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
| Cc: | "pgsql-admin(at)lists(dot)postgresql(dot)org" <pgsql-admin(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: managing multiple db developers |
| Date: | 2019-01-15 20:16:18 |
| Message-ID: | 1504617051.14816.1547583378151@mail.yahoo.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
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(dot)g(dot)johnston(at)gmail(dot)com> 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 | Mark Phillips | 2019-01-15 20:29:12 | Re: managing multiple db developers |
| Previous Message | Ron | 2019-01-15 18:48:04 | Re: Delete Enhancement Request |