Simple database, multiple instances?

Поиск
Список
Период
Сортировка
От Mario Splivalo
Тема Simple database, multiple instances?
Дата
Msg-id 4CF244DA.70206@megafon.hr
обсуждение исходный текст
Ответы Re: Simple database, multiple instances?  (Dimitri Fontaine <dimitri@2ndQuadrant.fr>)
Re: Simple database, multiple instances?  (Maciek Sakrejda <msakrejda@truviso.com>)
Список pgsql-performance
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

В списке pgsql-performance по дате отправления:

Предыдущее
От: Greg Smith
Дата:
Сообщение: Re: CPUs for new databases
Следующее
От: Mario Splivalo
Дата:
Сообщение: SELECT INTO large FKyed table is slow