patternsqlMinor
Maximum number of databases for single instance of PostgreSQL 9
Viewed 0 times
postgresqlnumbermaximumdatabasesinstancesinglefor
Problem
Developing a multicustomer application we plan to use a different database for each customer.
But it could be more than 1000 customers (applications).
Will PostgreSQL handle it without any problems?
Has anybody tried something similar?
Note: 35 tables for each one, with up to 3000 records as an average, for each database.
But it could be more than 1000 customers (applications).
Will PostgreSQL handle it without any problems?
Has anybody tried something similar?
Note: 35 tables for each one, with up to 3000 records as an average, for each database.
Solution
I haven't tried it myself, but there are others around who have.
Here you can see that even 10,000 databases run without problem on a single instance. You can even find some pratical aspects on ServerFault as well.
Since your databases are quite small, you will not run into any sort of file number limitation of the host OS. The only problem I can think of is that when all these databases will be accessed concurrently, handling all those connections will be tricky.
And, as a last note: you are very welcome on this site. We hope you will remain with us for a long time.
Here you can see that even 10,000 databases run without problem on a single instance. You can even find some pratical aspects on ServerFault as well.
Since your databases are quite small, you will not run into any sort of file number limitation of the host OS. The only problem I can think of is that when all these databases will be accessed concurrently, handling all those connections will be tricky.
And, as a last note: you are very welcome on this site. We hope you will remain with us for a long time.
Context
StackExchange Database Administrators Q#23971, answer score: 9
Revisions (0)
No revisions yet.