| From: | Mark Phillips <mark(dot)phillips(at)mophilly(dot)com> |
|---|---|
| To: | "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:29:12 |
| Message-ID: | C8866C1C-3622-48E9-AA03-61C40831FF6C@mophilly.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On Jan 15, 2019, at 10:07 AM, David G. Johnston <david(dot)g(dot)johnston(at)gmail(dot)com> wrote:
>
> I recommend leveraging the fact that PostgreSQL lacks per-instance
> licensing fees and have each developer run (more or less)
Thank you for the suggestion.
That has worked for us to a degree. We ran into situations where the developer had configuration issues and/or the dba was able to determine where “missing” changes came from.
Cheers,
- Mark
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mark Phillips | 2019-01-15 20:31:16 | Re: managing multiple db developers |
| Previous Message | suresh neravati | 2019-01-15 20:16:18 | Re: managing multiple db developers |