| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Mark Phillips <mark(dot)phillips(at)mophilly(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 18:07:36 |
| Message-ID: | CAKFQuwZm4+AjjMateQ7-o24ogjfmgFYA2mt9qJtOtSt81LPmeA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
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 | S. Bob | 2019-01-15 18:14:04 | Re: managing multiple db developers |
| Previous Message | Pepe TD Vo | 2019-01-15 17:57:50 | Re: create tablespaces and users |