pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Bruno Wolff III <bruno@wolff.to>
To: Krishna R Palati <krishna@hedgehoghosting.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: Hot backup
Date: Wed, 2 Jun 2004 13:14:22 -0500
Message-ID: <20040602181422.GA12553@wolff.to> (raw)
In-Reply-To: <200406011455.i51EtUXg093018@mx1.hedgehoghosting.net>
References: <20040531091503.GA10575@wolff.to>
	<200406011455.i51EtUXg093018@mx1.hedgehoghosting.net>

On Tue, Jun 01, 2004 at 10:55:26 -0400,
  Krishna R Palati <krishna@hedgehoghosting.com> wrote:
> Hello,
> 
> Thanks for the reply. Pg_dump might provide consistent dump at that point of
> time. But my question is:
> 
> We can setup pg_dump everyday at 3AM. Suppose a crash occurs at 10PM. Is
> there a way in Postgres for us to use the dump file from 3AM and the
> transaction logs since then so that we can do a point in time recovery (to
> recover everything till 10PM) ? 

If you are talking about a system crash, you won't lose any committed
transactions and you don't need to reload from a dump at all. Just start
the server back up and it will recover.

If you are talking a head crash (or multiple ones taking out a raid set),
then you can only recover from the last dump, since the data that might
be used to roll forward from a dump will be lost.

If you are talking about going back to before an erroneous transaction ruined
the database, you can't do that now without going back to the last dump
or trying to fix the live version with new transactions. The next version
may have point in time recovery which would allow you to roll forward from
a dump to a particular time. We won't know for about a month if this
feature will make it in. The next version will be released sometime this fall.



view thread (8+ messages)  latest in thread

Message-ID: <20040602181422.GA12553@wolff.to>
Permalink:  ../20040602181422.GA12553@wolff.to/
Also on:    postgresql.org/message-id/20040602181422.GA12553@wolff.to

 · 

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: bruno@wolff.to, krishna@hedgehoghosting.com
  Subject: Re: Hot backup
  In-Reply-To: <20040602181422.GA12553@wolff.to>
  References: <20040531091503.GA10575@wolff.to> <200406011455.i51EtUXg093018@mx1.hedgehoghosting.net> <20040602181422.GA12553@wolff.to>

* 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