From: Russ Brown <pickscrape@gmail.com>
To: pgsql-general@postgresql.org
Subject: Re: Replication
Date: Tue, 13 Sep 2005 08:45:10 -0700
Message-ID: <4326F406.7010402@gmail.com> (raw)
In-Reply-To: <KGEFLMPJFBNNLNOOOPLGOEOGCIAA.simon@2ndquadrant.com>
References: <KGEFLMPJFBNNLNOOOPLGOEOGCIAA.simon@2ndquadrant.com>
Simon Riggs wrote:
> Barry,
>
> You can use PITR to archive transaction logs to a second server that is
> kept in standby mode.
>
> This will cope with any number of tables and cope with dynamic changes
> to tables.
>
> This is fairly straightforward and very low overhead.
> Set archive_command to a program that transfers xlog files to second
> server.
> Then set restore_command on the second server to a program that loops
> until the next file is available.
> Switchover time is low.
>
Apologies for going slighly off topic, but isn't this basically how
MySQL does replication? I ask because one of the arguments against
moving to PostgreSQL in my organisation is 'no replication out of the
box'. But if the above is true it seems that all that is required are a
couple of scripts to handle log transfer and you have a form of
replication out of the box right there.
Or am I missing something?
--
Russ
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-general@postgresql.org
Cc: pickscrape@gmail.com
Subject: Re: Replication
In-Reply-To: <4326F406.7010402@gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox