- Mailing list pgsql-hackers-pitr

From Simon Riggs
Subject
Date
Msg-id 000601c3f4e1$a9553b20$c19d87d9@LaptopDellXP
Whole thread Raw
In response to Re: Proposals for PITR  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re:  (Bruce Momjian <pgman@candle.pha.pa.us>)
List pgsql-hackers-pitr
>Tom Lane [mailto:tgl@sss.pgh.pa.us]
>Re: [pgsql-hackers-pitr] Proposals for PITR
>>"Simon Riggs" <simon@2ndquadrant.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


pgsql-hackers-pitr by date:

Previous
From: "Simon Riggs"
Date:
Subject: Re: Proposals for PITR
Next
From: Bruce Momjian
Date:
Subject: Re: