On Thu, May 07, 2009 at 09:45:30PM +0200, Anders Steinlein wrote:
> Has anyone done something like this, or is it simply A Bad Idea? How
> many schemas can a database contain, until one hits a (hard or soft)
> limit? Keep in mind that this is not a "regular" web-app with thousands
> of users, but more in the range of 500-1000 for the foreseeable future.
I'm doing something similarish for our blog server. We have a blog db and
a schema for each user. This was mainly for backup, restore and maintenance
reasons. Being able to take one dump of all the blogs and then selectively
rip them out by schema is nice.
Currently we're at 632 schemas and roles and climbing. No problems as yet.
--
"A search of his car uncovered pornography, a homemade sex aid, women's
stockings and a Jack Russell terrier."
- http://www.news.com.au/story/0%2C27574%2C24675808-421%2C00.html
--
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
