On 12/08/2011 10:26 PM, chester c young wrote:
have an db with about 15 tables that will handle many companies. no data
overlap between companies. is it more efficient run-time to use one database
and index each row by company id, and one database and partition each table by
company id, or to create a database for each company?
it is a web-based app using persistent connections. no copying.
If you post a question on Stack Overflow and on the mailing list, please
link to your stack overflow question from your mailing list post!
http://stackoverflow.com/questions/8432636/in-postgresql-are-partitions-or-multiple-databases-more-efficient/
That'll help avoid duplication of effort, and make it easier for people
searching for similar topics later to find out more.
--
Craig Ringer
