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.
Best Regards, Simon Riggs
> -----Original Message-----
> From: pgsql-general-owner@postgresql.org
> [mailto:pgsql-general-owner@postgresql.org]On Behalf Of
> barry@e-rm.co.uk
> Sent: 12 September 2005 04:52
> To: pgsql-general@postgresql.org
> Subject: [GENERAL] Replication
>
>
> Hi,
>
> I currently have a postgresql 8 system which I want to replicate
> (ideally in realtime) with a spare host in order to introduce some
> redundancy - eg. if the master server dies then I've got a ready-to-go
> backup. Switchover does not have to be automated.
>
> I've looked into commandprompt.com's mammoth system, but it only
> supports up to 1000 tables (the documentation doesn't mention this!) -
> the database in question has more than 1000 tables, and adds
> new tables
> regularly. Slony-I and pgpool apparently don't support dynamic
> schemas, which I'd obviously need, so they're not quite up to the job
> either.
>
> I'm currently looking at some sort of hack-job with the WAL archives
> (see http://www.issociate.de/board/index.php?t=msg&goto=443099), but
> this looks like a slightly flaky approach - have I missed the obvious
> solution? Is there any stable software available which can
> replicate a
> large and dynamic number of tables?
>
> Cheers,
>
> Barry
>
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 4: Have you searched our list archives?
>
> http://archives.postgresql.org
