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 1BBB3D1B438 for ; Wed, 21 Jul 2004 00:15:49 -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 69002-10 for ; Wed, 21 Jul 2004 03:15:44 +0000 (GMT) Received: from news.hub.org (news.hub.org [200.46.204.72]) by svr1.postgresql.org (Postfix) with ESMTP id 879D1D1B391 for ; Wed, 21 Jul 2004 00:15:43 -0300 (ADT) Received: from news.hub.org (news.hub.org [200.46.204.72]) by news.hub.org (8.12.9/8.12.9) with ESMTP id i6L3FRr3068237 for ; Wed, 21 Jul 2004 03:15:43 GMT (envelope-from news@news.hub.org) Received: (from news@localhost) by news.hub.org (8.12.9/8.12.9/Submit) id i6L2lKsf058665 for pgsql-admin@postgresql.org; Wed, 21 Jul 2004 02:47:20 GMT From: Gaetano Mendola X-Newsgroups: comp.databases.postgresql.admin Subject: Re: [HACKERS] Point in Time Recovery Date: Sat, 17 Jul 2004 11:39:07 +0200 Organization: PYRENET Midi-pyrenees Provider Lines: 37 Message-ID: <40F8F3BB.8030002@bigfoot.com> References: <200407132242.i6DMgg612564@candle.pha.pa.us> <1089760416.17493.3327.camel@stromboli> <40F49AE9.2060805@familyhealth.com.au> <1089789682.17493.3890.camel@stromboli> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: abuse@pyrenet.fr To: Simon Riggs User-Agent: Mozilla Thunderbird 0.7.1 (Windows/20040626) X-Accept-Language: en-us, en In-Reply-To: <1089789682.17493.3890.camel@stromboli> X-Enigmail-Version: 0.84.2.0 X-Enigmail-Supports: pgp-inline, pgp-mime To: pgsql-admin@postgresql.org X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200407/232 X-Sequence-Number: 14300 Simon Riggs wrote: > On Wed, 2004-07-14 at 03:31, Christopher Kings-Lynne wrote: > >>Can you give us some suggestions of what kind of stuff to test? Is >>there a way we can artificially kill the backend in all sorts of nasty >>spots to see if recovery works? Does kill -9 simulate a 'power off'? >> > > > I was hoping some fiendish plans would be presented to me... > > But please start with "this feels like typical usage" and we'll go from > there...the important thing is to try the first one. > > I've not done power off tests, yet. They need to be done just to > check...actually you don't need to do this to test PITR... > > We need to exhaustive tests of... > - power off > - scp and cross network copies > - all the permuted recovery options > - archive_mode = off (i.e. current behaviour) > - deliberately incorrectly set options (idiot-proof testing) If you write also how to perform these tests it's also good in order to show which problem PITR is addressing, I mean I know that is addressing a power off but how I will recover it ? Regards Gaetano Mendola