X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 4AC39D1B1F7 for ; Wed, 2 Jun 2004 15:08:51 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 45866-02 for ; Wed, 2 Jun 2004 18:08:51 +0000 (GMT) Received: from wolff.to (wolff.to [66.93.249.74]) by svr1.postgresql.org (Postfix) with SMTP id F214CD1B1DC for ; Wed, 2 Jun 2004 15:08:47 -0300 (ADT) Received: (qmail 12953 invoked by uid 500); 2 Jun 2004 18:14:22 -0000 Date: Wed, 2 Jun 2004 13:14:22 -0500 From: Bruno Wolff III To: Krishna R Palati Cc: pgsql-admin@postgresql.org Subject: Re: Hot backup Message-ID: <20040602181422.GA12553@wolff.to> Mail-Followup-To: Krishna R Palati , pgsql-admin@postgresql.org References: <20040531091503.GA10575@wolff.to> <200406011455.i51EtUXg093018@mx1.hedgehoghosting.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200406011455.i51EtUXg093018@mx1.hedgehoghosting.net> User-Agent: Mutt/1.5.6i X-Virus-Scanned: by amavisd-new at hub.org X-Archive-Number: 200406/14 X-Sequence-Number: 13674 On Tue, Jun 01, 2004 at 10:55:26 -0400, Krishna R Palati 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.