From: | "Simon Riggs" <simon(at)2ndquadrant(dot)com> |
---|---|
To: | "Tatsuo Ishii" <t-ishii(at)sra(dot)co(dot)jp> |
Cc: | <barry(at)e-rm(dot)co(dot)uk>, <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Replication |
Date: | 2005-09-13 23:21:04 |
Message-ID: | KGEFLMPJFBNNLNOOOPLGIEOPCIAA.simon@2ndquadrant.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
> From: Tatsuo Ishii [mailto:t-ishii(at)sra(dot)co(dot)jp]
> > 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.
>
> I thought there are some issues of log based replication (I don't
> remeber details though). Have they been resolved recently?
Yes, currently log-file based replication is not recommended when the
transaction rate is either low or extremely variable.
I was regrettably unable to get a patch for that into 8.1
Best Regards, Simon Riggs
From | Date | Subject | |
---|---|---|---|
Next Message | Stephen Frost | 2005-09-13 23:23:52 | Re: oracle's first_value function for postgres? |
Previous Message | Brent Wood | 2005-09-13 22:17:04 | Re: Pushing result set to table on different machine? |