Skip site navigation (1) Skip section navigation (2)


From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: simon(at)2ndquadrant(dot)com
Cc: "'Tom Lane'" <tgl(at)sss(dot)pgh(dot)pa(dot)us>,pgsql-hackers-pitr(at)postgresql(dot)org
Subject: Re:
Date: 2004-02-17 19:40:14
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackerspgsql-hackers-pitr
Simon Riggs wrote:
> >Tom Lane [mailto:tgl(at)sss(dot)pgh(dot)pa(dot)us]
> >Re: [pgsql-hackers-pitr] Proposals for PITR
> >>"Simon Riggs" <simon(at)2ndquadrant(dot)com> writes:
> >> The general PITR recovery scenario requires:
> >> A - Take a full database backup
> >> B - Take regular log file backups
> >> C - Restore a full backup of a database.
> > Note that pg_dump has absolutely zero to do with this.  The base for a
> > PITR recovery scenario has to be a physical dump, not a logical dump;
> > else WAL replay won't work.
> Yes, I agree, I only included it because it was on the TODO. I'll cut it
> out of the further thinking on PITR, in case it confuses the issue in
> design/usage.

I removed the pg_dump mention on the web page.  Thanks.

  Bruce Momjian                        |
  pgman(at)candle(dot)pha(dot)pa(dot)us               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073

In response to

  • at 2004-02-16 23:07:25 from Simon Riggs

pgsql-hackers by date

Next:From: Bruce MomjianDate: 2004-02-17 19:50:09
Subject: Re: log_line_info
Previous:From: Andrew DunstanDate: 2004-02-17 17:45:20
Subject: log_line_info

pgsql-hackers-pitr by date

Next:From: Simon RiggsDate: 2004-02-17 22:41:17
Subject: Archival API
Previous:From: Simon RiggsDate: 2004-02-16 23:07:25
Subject: Re: Proposals for PITR

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group