A-Original-Client-UID: 188.129.74.222 splivalo
Message-ID: <4CF244DA.70206@megafon.hr>
Date: Sun, 28 Nov 2010 13:02:34 +0100
From: Mario Splivalo <mario.splivalo@megafon.hr>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US;
	rv:1.9.1.15) Gecko/20101027 Lightning/1.0b1 Thunderbird/3.0.10
MIME-Version: 1.0
To: pgsql-performance@postgresql.org
Subject: Simple database, multiple instances?
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

I have simple database schema, containing just three tables:

samples, drones, drones_history.

Now, those tables hold data for the drones for a simulation. Each 
simulation dataset will grow to around 10 GB in around 6 months.

Since the data is not related in any way I was thinking in separating 
each simulation into it's own database. That way it would be much easier 
for me to, at later date, move some of the databases to other servers 
(when dataset grows beyond the original server storage capacity limit).

But. At this time I have around 600 simulations, that would mean 
creating 600 databases, and in future there could very well be around 
5000 simulations. Is postgres going to have 'issues' with that large 
number of databases?

Or do I model my system in a way that each database holds around 100 
simulations?

	Mario