Search Postgresql Archives

Re: Schema per user?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Adam Ruth <adamruth@xxxxxxx> writes:
> I've actually done this before. I had a web app with about 400 users  
> each with their own schema. It actually worked very well, except for  
> one thing. There got to be so many tables that a pg_dump would fail  
> because it would run out of file locks. We got around it by creating a  
> primary table and then using views in each of the schemas to access  
> that user's data. It also made it easy to do a query against all users  
> at once in the primary table.

Note that this is about how many tables you have, and has got nothing to
do with how many schemas they are in, but: the solution to that is to
increase max_locks_per_transaction.  The default value is kinda
conservative to avoid eating up too much shared memory.

			regards, tom lane

-- 
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux