Re: Big 7.4 items
Greg Copeland <greg@copelandconsulting.net>
From: Greg Copeland <greg@CopelandConsulting.Net>
To: Hannu Krosing <hannu@tm.ee>
Cc: Bruce Momjian <pgman@candle.pha.pa.us>, PostgreSQL-development <pgsql-hackers@postgresql.org>, kward@peerdirect.com, patrickm@redhat.com, darren@up.hrcoxmail.com, Jan Wieck <JanWieck@Yahoo.com>, jrnield@usol.com
Date: 2002-12-16T13:56:25Z
Lists: pgsql-hackers
On Fri, 2002-12-13 at 04:53, Hannu Krosing wrote: > On Fri, 2002-12-13 at 06:22, Bruce Momjian wrote: > > I wanted to outline some of the big items we are looking at for 7.4: > > Point-In-Time Recovery (PITR) > > > > J. R. Nield did a PITR patch late in 7.3 development, and Patrick > > MacDonald from Red Hat is working on merging it into CVS and > > adding any missing pieces. Patrick, do you have an ETA on that? > > How hard would it be to extend PITR for master-slave (hot backup) > repliaction, which should then amount to continuously shipping logs to > slave and doing nonstop PITR there :) > > It will never be usable for multi-master replication, but somehow it > feels that for master-slave replication simple log replay would be most > simple and robust solution. 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? -- Greg Copeland <greg@copelandconsulting.net> Copeland Computer Consulting