| From: | Shridhar Daithankar <shridhar_daithankar(at)persistent(dot)co(dot)in> |
|---|---|
| To: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Big 7.4 items |
| Date: | 2002-12-16 14:02:58 |
| Message-ID: | 200212161932.58595.shridhar_daithankar@persistent.co.in |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Monday 16 December 2002 07:26 pm, you wrote:
> I'm curious, what would be the recovery strategy for PITR master-slave
> replication should the master fail (assuming hot fail over/backup)? A
> simple dump/restore? Are there/is there any facilities in PorstgreSQL
> for PITR archival which prevents PITR logs from be recycled (or perhaps,
> simply archived off)? What about PITR streaming to networked and/or
> removable media?
In asynchrounous replication, WAL log records are fed to anoter host, which
replays those transactions to sync the data. This way it does not matter if
WAL log is recycled as it is already replicated someplace else..
HTH
Shridhar
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Copeland | 2002-12-16 14:13:13 | Re: Big 7.4 items |
| Previous Message | Greg Copeland | 2002-12-16 13:56:25 | Re: Big 7.4 items |