pg.ddx.io  pgsql-hackers-pitr@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Simon Riggs <simon@2ndquadrant.com>
To: 'Tom Lane' <tgl@sss.pgh.pa.us>
Cc: pgsql-hackers-pitr@postgresql.org
Date: Mon, 16 Feb 2004 23:07:25 -0000
Message-ID: <000601c3f4e1$a9553b20$c19d87d9@LaptopDellXP> (raw)
In-Reply-To: <9293.1076868784@sss.pgh.pa.us>

>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




view thread (37+ messages)  latest in thread

Message-ID: <000601c3f4e1$a9553b20$c19d87d9@LaptopDellXP>
Permalink:  ../000601c3f4e1$a9553b20$c19d87d9@LaptopDellXP/
Also on:    postgresql.org/message-id/000601c3f4e1$a9553b20$c19d87d9@LaptopDellXP

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-hackers-pitr@postgresql.org
  Cc: simon@2ndquadrant.com, tgl@sss.pgh.pa.us
  Subject: Re: 
  In-Reply-To: <000601c3f4e1$a9553b20$c19d87d9@LaptopDellXP>
  References: <9293.1076868784@sss.pgh.pa.us> <000601c3f4e1$a9553b20$c19d87d9@LaptopDellXP>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox