However, what is the max number of database I can create before
performance goes down?
I know I'm not directly answering your question, but you might want to
consider why you're splitting things up into different logical
databases. If security is a big concern, you can create different
da
On 11/18/05, anon permutation <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> We want to create a database for each one of our departments, but we only
> want to have one instance of postgresql running. There are about 10-20
> departments. I can easily use createdb to create these databases. However,
>
On Nov 19, 2005, at 12:24 , anon permutation wrote:
However, what is the max number of database I can create before
performance goes down?
Assuming each database is performing well alone, how would putting
10-20 of them together in one instance affect postgres?
In terms of getting a new
Hi,
We want to create a database for each one of our departments, but we only
want to have one instance of postgresql running. There are about 10-20
departments. I can easily use createdb to create these databases. However,
what is the max number of database I can create before performance
