pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Mark Kirkwood <markir@coretech.co.nz>
To: Simon Riggs <simon@2ndquadrant.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-hackers@postgresql.org
Subject: Re: PITR COPY Failure (was Point in Time Recovery)
Date: Wed, 21 Jul 2004 14:39:18 +1200
Message-ID: <40FDD756.9030005@coretech.co.nz> (raw)
In-Reply-To: <1090333179.28049.2905.camel@stromboli>
References: <200407141555.i6EFtnk22984@mail.osdl.org>
	<1089833620.17493.4624.camel@stromboli>
	<40F5E14A.4090003@coretech.co.nz>
	<1089875702.17493.5539.camel@stromboli>
	<40F652C6.4070007@coretech.co.nz>
	<1089935215.17493.6906.camel@stromboli>
	<40FA0F93.8010607@coretech.co.nz>
	<40FC6BF2.5050701@coretech.co.nz>
	<3607.1090296869@sss.pgh.pa.us>
	<1090324635.28049.2554.camel@stromboli>
	<7787.1090327914@sss.pgh.pa.us>
	<1090329086.28049.2708.camel@stromboli>
	<1090333179.28049.2905.camel@stromboli>

This is presumably a standard feature of any PITR design - if the 
failure event destroys the current transaction log, then you can only 
recover transactions that committed in the last *archived* log.

regards

Mark

Simon Riggs wrote:

>
>The test works, but gives what looks like strange results: the test
>blows away the data directory completely, so the then-current xlog dies
>too. That contained the commit for the large COPY, so even though the
>recovery now works, the table has zero rows in it. (When things die
>you're still likely to lose *some* data).
>
>
>
>  
>



view thread (19+ messages)  latest in thread

Message-ID: <40FDD756.9030005@coretech.co.nz>
Permalink:  ../40FDD756.9030005@coretech.co.nz/
Also on:    postgresql.org/message-id/40FDD756.9030005@coretech.co.nz

 · 

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-admin@postgresql.org
  Cc: markir@coretech.co.nz, simon@2ndquadrant.com, tgl@sss.pgh.pa.us, pgsql-hackers@postgresql.org
  Subject: Re: PITR COPY Failure (was Point in Time Recovery)
  In-Reply-To: <40FDD756.9030005@coretech.co.nz>
  References: <200407141555.i6EFtnk22984@mail.osdl.org> <1089833620.17493.4624.camel@stromboli> <40F5E14A.4090003@coretech.co.nz> <1089875702.17493.5539.camel@stromboli> <40F652C6.4070007@coretech.co.nz> <1089935215.17493.6906.camel@stromboli> <40FA0F93.8010607@coretech.co.nz> <40FC6BF2.5050701@coretech.co.nz> <3607.1090296869@sss.pgh.pa.us> <1090324635.28049.2554.camel@stromboli> <7787.1090327914@sss.pgh.pa.us> <1090329086.28049.2708.camel@stromboli> <1090333179.28049.2905.camel@stromboli> <40FDD756.9030005@coretech.co.nz>

* 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