Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gjV8R-00073K-1A for pgsql-admin@arkaria.postgresql.org; Tue, 15 Jan 2019 20:16:31 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1gjV8O-0001if-5h for pgsql-admin@arkaria.postgresql.org; Tue, 15 Jan 2019 20:16:28 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gjV8N-0001eV-Gx for pgsql-admin@lists.postgresql.org; Tue, 15 Jan 2019 20:16:27 +0000 Received: from sonic310-14.consmr.mail.bf2.yahoo.com ([74.6.135.124]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gjV8K-0005b3-4r for pgsql-admin@lists.postgresql.org; Tue, 15 Jan 2019 20:16:27 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1547583381; bh=qDR0uY+CU2btqU/tCIWnU5EhLzEBP93PAWpkZhAbEJ8=; h=Date:From:To:Cc:In-Reply-To:References:Subject:From:Subject; b=iQIoifN2RIm0mCaD8UU18WwVE6+GTEenScacnR+0BcrqoNeo93JO6Oxi4Brv5c8TW9XcaFk63qFDOE3ArmfBNpv04Q0TWUik4EpHTwDAr8FuEq0izneNhY6XZSR3hN7zvokOJ3C55SJSkXnQN4OKO9uvWm1TWYs5mn7ROkIOoCdY67TOaIK2gT1vZHMpPc99/O3RqOTkeh/SzTsirjZ6/lMM0TFIN5rXkX1wdOhSjybvsL3bEWxcBXmHuGOpvkqOzZGNsZz67NIe9pw4h5oJL4mncAWQ/XZWrT1Ki6NSDZvKteP1lE3Tw/8GSgk91zx09aQpwPWPJYpr5mWapGaM0w== X-YMail-OSG: wN08ne8VM1mowW1PyLKdPKAsR0aFqR59OKIen2ZTGxxCjDOt00jfGiy3BvSmItE C7Ptjlc2bVgpTpO1Ek0EJmwHYx_O5UGbb1ATMsfWFwfRSF16PkSI62DjaWvYmsQT7mGXbDb8VKLQ jv2PxRgYEPNs0hBjaLyB_yCzy13OWaqA3PdKuuZ_CByNMkWEISmhg9OFpnI7v3HECyqLkZq3NHv. gfhkYHugNxbD4tO8QBmHPRoafWjWYzByBRKZHpfqOXEyByIiT0stejpTGZ.MGIjKoP1_Eq0J9ITi Ud4lXkdL.vk.02oL3CCVlEk72Df3rxJh4DueseiGdmXyFZfskmgg3aP38DU.RT4gbipfV6yVr_rG TGFODyG7MSkzslzbtKRgLHzu6_C3vDC1v9B86Luxuoo9jpzJpMfd2N68rgS71O9QLYKO_lf95QGl 1RF4xSsyow1UusVqlK8vJ77MP4btCJvDrmkdNKM6p9ri.mxL78nZ875CSJiBN50kRiMW6QFhw3LC OBUjoy3nOQqr8Yc3D5m4sdIdmzX1fzxfJJbVDaTH4.sx.xSBI0N.pL7e045Q._sa_p7bqtlUT56v GuTWCLl7kVQu_tMrRMyS2pI8vltpslex3eLufz_4my3cCsR86V7AYfrr9rvwvZn17JN3ig5NStaO pzSACn1upE6mFXi1tzSbrPl3ratGh4ri4gs7doIbRTTjnWg9G6cKBCkxHaDi.pSj90Ye4KYIxhGQ X6c8FGsGicMZtzH6HYxy9ns3MbZCu7ctsKoGmA7rkIHoSzJQfJKFJw9uBnJGxVYX0CyGO_3yWda2 iXuLYRkFDNPQXRmZS7s0Fd3gpsud63m_q0cou3hMMmNBHtXrEFaq2XegBm2mopa9J68KX0aO3aIq sSSHeDWYndO7l2.ov9T7u1G2f2BUMJx9rfpZZbvU.oivZ4S22XEpV.uMbq6mLpvGW4BlpLpWAyf4 zJK7ajCV9musaNZvablvx29xVQjJDN2xgLt83T7_CdzRpFWMMHdWWw9ecZL6NL0nzBAf1DvMQKlB 4VAuwXngZfGFzOp8ALuIqavcqqQEFKt9P6f_EPbuKrgPZgsSIjozWHe1NCVH88qaLGn.vVNHWiZ. erm0qA0onySyE Received: from sonic.gate.mail.ne1.yahoo.com by sonic310.consmr.mail.bf2.yahoo.com with HTTP; Tue, 15 Jan 2019 20:16:21 +0000 Date: Tue, 15 Jan 2019 20:16:18 +0000 (UTC) From: suresh neravati To: Mark Phillips , "David G. Johnston" Cc: "pgsql-admin@lists.postgresql.org" Message-ID: <1504617051.14816.1547583378151@mail.yahoo.com> In-Reply-To: References: Subject: Re: managing multiple db developers MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_14815_1943690195.1547583378149" X-Mailer: WebService/1.1.12857 YMailNorrin Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:64.0) Gecko/20100101 Firefox/64.0 Content-Length: 3454 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk ------=_Part_14815_1943690195.1547583378149 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable You can create individual database for each developer.=C2=A0 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 wrote: =20 =20 On Tue, Jan 15, 2019 at 10:44 AM Mark Phillips wrote: > > When I worked for an Oracle shop, the dba set up individual =E2=80=9Csche= mas=E2=80=9D for each developer. That allowed us a database instance of our= own for experiments, including modifying stored procedures and such, witho= ut 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 clu= ster. 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. =20 ------=_Part_14815_1943690195.1547583378149 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
You can create individual database for each developer.  T= hat works as a cluster, but you can specify smaller memory numbers for each= developer.

=20
=20
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> wrot= e:
>
> When I worked for an Oracl= e shop, the dba set up individual =E2=80=9Cschemas=E2=80=9D for each develo= per. That allowed us a database instance of our own for experiments, includ= ing modifying stored procedures and such, without the risk of negative impa= ct on other developers or modifying the stable dev-test and QA databases.>
> I am wondering how to accompli= sh 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 m= achine

David J.

------=_Part_14815_1943690195.1547583378149--