Received: from maia.hub.org (maia-2.hub.org [200.46.204.251])
	by mail.postgresql.org (Postfix) with ESMTP id A4ADA1337B51
	for <pgsql-performance-postgresql.org@mail.postgresql.org>;
	Tue, 30 Nov 2010 07:46:12 -0400 (AST)
Received: from mail.postgresql.org ([200.46.204.86])
	by maia.hub.org (mx1.hub.org [200.46.204.251]) (amavisd-maia,
	port 10024) with ESMTP id 80210-07
	for <pgsql-performance-postgresql.org@mail.postgresql.org>;
	Tue, 30 Nov 2010 11:46:05 +0000 (UTC)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.6
Received: from acidenitrix.villemain.org (acidenitrix.villemain.org
	[91.121.90.165])
	by mail.postgresql.org (Postfix) with ESMTP id 4E17F1336B42
	for <pgsql-performance@postgresql.org>;
	Tue, 30 Nov 2010 07:46:04 -0400 (AST)
Received: from 89-158-241-48.rev.dartybox.com ([89.158.241.48]
	helo=DimIMac.local) by acidenitrix.villemain.org with esmtpsa
	(TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.69)
	(envelope-from <dimitri@2ndQuadrant.fr>)
	id 1PNOep-0007Cp-Kc; Tue, 30 Nov 2010 12:46:03 +0100
Received: by DimIMac.local (Postfix, from userid 501)
	id E8F5C12DB039; Tue, 30 Nov 2010 12:45:57 +0100 (CET)
From: Dimitri Fontaine <dimitri@2ndQuadrant.fr>
To: Mario Splivalo <mario.splivalo@megafon.hr>
Cc: pgsql-performance@postgresql.org
Subject: Re: Simple database, multiple instances?
Organization: 2ndQuadrant
References: <4CF244DA.70206@megafon.hr>
User-Mail-Address: dimitri@2ndQuadrant.fr
Date: Tue, 30 Nov 2010 12:45:57 +0100
In-Reply-To: <4CF244DA.70206@megafon.hr> (Mario Splivalo's message of "Sun, 28
	Nov 2010 13:02:34 +0100")
Message-ID: <m2d3pnavbe.fsf@2ndQuadrant.fr>
User-Agent: Gnus/5.110011 (No Gnus v0.11) Emacs/24.0.50 (darwin)
MIME-Version: 1.0
Content-Type: text/plain
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Spam-Status: No, hits=-1.9 tagged_above=-10 required=5 tests=BAYES_00=-1.9
X-Spam-Level: 
X-Archive-Number: 201011/406
X-Sequence-Number: 41430

Mario Splivalo <mario.splivalo@megafon.hr> writes:
> 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).

Do you intend to run queries across multiple simulations at once? If
yes, you want to avoid multi databases. Other than that, I'd go with a
naming convention like samples_<simulation id> and maybe some
inheritance to ease querying multiple simulations.

Regards,
-- 
Dimitri Fontaine
http://2ndQuadrant.fr     PostgreSQL : Expertise, Formation et Support