Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.databases.postgresql > #360

Re: Split database content without outage

Show all headers | View raw

On 05/29/2012 09:32 PM, igor.shmain@gmail.com wrote:
> I need to design a solution for a database which will grow and will require a horizontal split at some moment.

Require the split because of what?

> Here is how I am planning to do it: Every record in every table has a shard number. After the database becomes too large (gets too many requests), the tables need to be horizontally split. It means that for every table all records with some specific shard numbers need to be moved to a new database.
> My plan is to (1) create a copy of the database on a new server (backup/restore?), (2) synchronize the databases (how?), and then (3) forward all requests for the moved shards to the new database. (I will get rid of the unneeded shards later). An important requirement: there should be no outage for the users.

This cannot work since at least at one point you have to reconfigure 
clients to access a second (third, fourth...) database.  Why do you 
think you need to split the DB?  Did you consider using table 
partitioning instead?  Or did you consider deleting old data?

Kind regards

	robert

Back to comp.databases.postgresql | Previous | Next — Previous in thread | Next in thread | Find similar

Thread

Split database content without outage igor.shmain@gmail.com - 2012-05-29 12:32 -0700
  Re: Split database content without outage Robert Klemme <shortcutter@googlemail.com> - 2012-05-29 22:47 +0200
  Re: Split database content without outage Mladen Gogala <gogala.mladen@gmail.com> - 2012-06-04 23:17 +0000

csiph-web