Re: Very high latency, low bandwidth replication

From: Stuart Bishop <stuart(at)stuartbishop(dot)net>
To: Bob Jolliffe <bobjolliffe(at)gmail(dot)com>
Cc: "List, Postgres" <pgsql-general(at)postgresql(dot)org>
Subject: Re: Very high latency, low bandwidth replication
Date: 2014-07-02 08:46:51
Message-ID: CADmi=6MKThuJtmG0oqXquTMVJoD1xnsczNHyL-L5d3zgnnncRw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 30 June 2014 15:05, Bob Jolliffe <bobjolliffe(at)gmail(dot)com> wrote:

> What are people's thoughts about a more optimal solution? I would like to
> use a more incremental approach to replication. This does not have to be a
> "live" replication .. asynchronously triggering once every 24 hours is
> sufficient. Also there are only a subset of tables which are required (the
> rest consist of data which is generated).

WAL shipping is probably best here. Configure an archive_command on
the master to compress and push logs to cloud storage, and configure
a hot standby on site to pull and decompress the logs. The wal-e tool
may make things simpler pushing to cloud storage, or just follow the
PostgreSQL documentation to archive the WAL files to a filesystem.

If that isn't good enough, you can look at more esoteric approaches
(eg. nightly plaintext dumps to a git repository, pushing changes to
disk on site).

--
Stuart Bishop <stuart(at)stuartbishop(dot)net>
http://www.stuartbishop.net/

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Adrian Klaver 2014-07-02 13:14:34 Re: How can I replace the year of the created_at column with the current year dynamically ?
Previous Message Arup Rakshit 2014-07-02 07:48:08 Re: How can I replace the year of the created_at column with the current year dynamically ?