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

From: "Simon Riggs" <simon(at)2ndquadrant(dot)com>
To: "'Tom Lane'" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: <pgsql-hackers-pitr(at)postgresql(dot)org>
Subject:
Date: 2004-02-16 23:07:25
Message-ID: 000601c3f4e1$a9553b20$c19d87d9@LaptopDellXP (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-hackers-pitr
>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.

Regards, Simon


In response to

Responses

  • Re: at 2004-02-17 19:40:14 from Bruce Momjian

pgsql-hackers by date

Next:From: markwDate: 2004-02-16 23:41:07
Subject: Re: Proposed Query Planner TODO items
Previous:From: Simon RiggsDate: 2004-02-16 23:07:24
Subject: Re: Slow DROP INDEX

pgsql-hackers-pitr by date

Next:From: Bruce MomjianDate: 2004-02-17 19:40:14
Subject: Re:
Previous:From: Tom LaneDate: 2004-02-15 18:13:04
Subject: Re: Proposals for PITR

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