Re: Switching roles as an replacement of connection pooling tools - Mailing list pgsql-general

From CN
Subject Re: Switching roles as an replacement of connection pooling tools
Date
Msg-id 1464786451.556435.624726817.5B58E3ED@webmail.messagingengine.com
Whole thread Raw
In response to Re: Switching roles as an replacement of connection pooling tools  (Melvin Davidson <melvin6925@gmail.com>)
List pgsql-general
On Tue, May 31, 2016, at 10:23 PM, Melvin Davidson wrote:
That being said, IMHO, I believe having a separate schema for every user is poor database design
 
This is the best arrangement I can think of now for my use case:
 
1. Each schema holds an application independent from other schemas within the same database.
2. Each schema is fully controlled by a role who is responsible for the development of that application.
 
Best Regards,
CN
-- 
http://www.fastmail.com - The professional email service

pgsql-general by date:

Previous
From: CN
Date:
Subject: Re: Switching roles as an replacement of connection pooling tools
Next
From: "David G. Johnston"
Date:
Subject: Re: Switching roles as an replacement of connection pooling tools