I don't know abou the 'safe' in that list there. You will definitely need
to stop both postmasters from running while you are rsyncing and then start
them again afterwards, since memory contents will be different. You would
also need to rsync all the WAL files, the pg_controldata file, the
architecture must be identical, etc.
ie. What you are proposing is a very, very bad idea.
I know that Gavin is tinkering with a log shipping solution based on WAL at
the moment, that would be much better for your needs. Don't except it any
time soon tho :) It won't work at all until PITR goes in...
Chris
> -----Original Message-----
> From: pgsql-general-owner@postgresql.org
> [mailto:pgsql-general-owner@postgresql.org]On Behalf Of Jason Hihn
> Sent: Tuesday, 28 January 2003 12:56 PM
> To: pgsql-general@postgresql.org
> Subject: [GENERAL] Using RSYNC for replication?
>
>
> A sequence of events ocurred to me today that left me wondering if I can
> rsync the raw files as a form of replication. I'd like to keep
> postmaster running, but flush and lock everything, then perform the copy
> via rsync so only the new data is propigated, all while postmaster is
> running.
>
> In general, data is only added to a few tables in the database, with
> updates occuring infrequently to the rest. Rarely are deletes ever done.
> During the sync neither DB will change except as part of the rsync.
>
> I think this would be a quick, dirty, safe and efficient way to
> accomplish this without having to take down postmaster and send the
> whole shebang over.
>
> Are people using this? Will it work? Is it feasible? Thoughts?
>
> Many thanks in advance,
> -Jason
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 1: subscribe and unsubscribe commands go to majordomo@postgresql.org
>