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


Groups > comp.databases.postgresql > #359

Split database content without outage

Path csiph.com!newsfeed.hal-mli.net!feeder3.hal-mli.net!newsfeed.hal-mli.net!feeder1.hal-mli.net!npeer01.iad.highwinds-media.com!news.highwinds-media.com!feed-me.highwinds-media.com!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail
From igor.shmain@gmail.com
Newsgroups comp.databases.postgresql
Subject Split database content without outage
Date Tue, 29 May 2012 12:32:06 -0700 (PDT)
Organization http://groups.google.com
Lines 17
Message-ID <767f369f-5ff9-4fbf-aae1-3fc868293139@googlegroups.com> (permalink)
NNTP-Posting-Host 174.118.17.120
Mime-Version 1.0
Content-Type text/plain; charset=ISO-8859-1
Content-Transfer-Encoding quoted-printable
X-Trace posting.google.com 1338322418 1220 127.0.0.1 (29 May 2012 20:13:38 GMT)
X-Complaints-To groups-abuse@google.com
NNTP-Posting-Date Tue, 29 May 2012 20:13:38 +0000 (UTC)
Cc Igor Bertnyk <igor.bertnyk@gmail.com>, Andy Elkin <aelkin@gmail.com>
Complaints-To groups-abuse@google.com
Injection-Info glegroupsg2000goo.googlegroups.com; posting-host=174.118.17.120; posting-account=nf_7wQoAAABe0yM3jJUn2ICGdXv20Hcc
User-Agent G2/1.0
X-Received-Bytes 1875
Xref csiph.com comp.databases.postgresql:359

Show key headers only | View raw


Can you please help with advice? 
I need to design a solution for a database which will grow and will require a horizontal split at some moment. 
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.
What are the ways to achieve it?

Thank you in advance,
-igorS

Back to comp.databases.postgresql | Previous | NextNext 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