Skip site navigation (1) Skip section navigation (2)

Re: advice on Replication for a Specific Scenario

From: Greg Sabino Mullane <greg(at)endpoint(dot)com>
To: Donald Kerr <donald(dot)kerr(at)dkerr(dot)co(dot)uk>
Cc: pgsql-cluster-hackers(at)postgresql(dot)org
Subject: Re: advice on Replication for a Specific Scenario
Date: 2012-03-10 03:11:03
Message-ID: 20120310031103.GX3218@tinybird.home (view raw or flat)
Thread:
Lists: pgsql-cluster-hackerspgsql-general
On Mon, Feb 27, 2012 at 09:38:50PM -0000, Donald Kerr wrote:
> Hopefully this question is posted in the correct list. Apologies if that's
> not the case.

This is a fairly inactive list. You might have better responses on 
pgsql-general(at)postgresql(dot)org, but I will take a swing at things.

> The scenario is a server (master database - PostgreSQL/PostGIS) containing
> gis information (lots of it - Maybe up to 80Gb in about 25 tables). This
> serves maps to clients across an internal intranet. There are also 200
> clients (maybe up to 400 in the future) that are mobile, i.e. in vehicles,
> each with there own readonly copy of PostgreSQL/PostGIS serving maps locally
> on the vehicles. If I update tables with fresh information on the master, on
> a quarterly basis, I would like these updates to be trickled out to the
> copies that exist on the vehicles. The vehicles are on wireless lan for
> about 80% of the time but are out and about for the other 20%.

You are only applying changes to the master every quarter? The easiest solution 
is to apply those changes on the readonly databases as well, e.g. with a 
single file full of SQL commands. However, if you need something more automatic, 
your best bet for partial replication is Slony or Bucardo. If by "trickle" 
you mean that the client may get disconnected before it can completely sync 
with the master, then Slony is your best bet, as Bucardo will want to make 
all changes at once while Slony will attempt to "replay" the actual changes.

It's hard to say more however, without more details on your situation and 
requirement. Feel free to ask here or -general. I suspect that everyone 
on this list reads -general anyway. :)

-- 
Greg Sabino Mullane greg(at)endpoint(dot)com
End Point Corporation
PGP Key: 0x14964AC8

In response to

Responses

pgsql-cluster-hackers by date

Next:From: Donald KerrDate: 2012-03-10 08:16:00
Subject: Re: advice on Replication for a Specific Scenario
Previous:From: Michael PaquierDate: 2012-02-29 01:43:48
Subject: Re: 3rd Cluster Hackers Summit, May 15th in Ottawa

pgsql-general by date

Next:From: PgSQLDate: 2012-03-10 03:48:24
Subject: Re: Error installing postgresq91-python package
Previous:From: Kiriakos GeorgiouDate: 2012-03-09 23:48:21
Subject: Re: Regarding NOTIFY

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group