X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by postgresql.org (Postfix) with ESMTP id 8F54511F65E5 for ; Thu, 13 Apr 2006 05:00:33 -0300 (ADT) X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Score: 1.713 X-Spam-Level: * X-Spam-Status: No, score=1.713 required=5 tests=[RCVD_IN_NJABL_DUL=1.713] Received: from postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 83VGrlRH8GC9 for ; Thu, 13 Apr 2006 05:00:22 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from p0f.net (p0f.net [193.77.154.190]) by postgresql.org (Postfix) with ESMTP id DA16911F65E4 for ; Thu, 13 Apr 2006 05:00:23 -0300 (ADT) Received: from [10.10.190.53] ([193.77.165.58]) (authenticated bits=0) by p0f.net (8.13.3/8.13.3) with ESMTP id k3D7JnY6024596 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 13 Apr 2006 09:19:51 +0200 Message-ID: <443E053D.4080506@p0f.net> Date: Thu, 13 Apr 2006 10:01:01 +0200 From: Grega Bremec Organization: P0F User-Agent: Mozilla Thunderbird 1.0 (X11/20041207) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Rajesh Kumar Mallah CC: pgsql-admin@postgresql.org Subject: Re: FW: Setting up of PITR system. References: <442B93DD.4020305@p0f.net> <442E1945.4030006@p0f.net> <442FDC7F.9010001@p0f.net> <4430BC59.7040006@p0f.net> <4437AF15.3020707@p0f.net> In-Reply-To: X-Enigmail-Version: 0.93.0.0 OpenPGP: id=E077F97A Content-Type: text/plain; charset=ISO-8859-2 Content-Transfer-Encoding: 7bit X-Archive-Number: 200604/118 X-Sequence-Number: 21287 -----BEGIN PGP SIGNED MESSAGE----- Hash: RIPEMD160 Rajesh Kumar Mallah wrote: > Is cluttering of the wal archive area in cases where that backup > had to be re-started for whatever reasons is the *only* concern ? Well, yes, to be honest. But it may in consequence cause problems of another kind, which I don't feel qualified to reassure you on: I am not positive about what happens if you try to replay an old WAL on a current database backup. If nothing else, it is going to make the person restoring the backup rather unnerved about success of the operation they are currently performing, which is not a good thing, IMHO. They are restoring a backup afterall, which means they'd already undergone a fair amount of stress as it is. :) End all, it is your choice to decide which is more trouble and which is worth more: fixing the script to produce clean backups or informing your backup operators about the extra care they need to take when restoring backups. > Please do not put too much effort, as i the drives in my other > server has got installed and i am adapting the script for doing > remote backup ( which is a more common senerio). Very nice! How is it going? And how are you copying the WALs? scp? rsync? Kind regards, - -- Grega Bremec gregab at p0f dot net -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) iD8DBQFEPgU9fu4IwuB3+XoRA+MeAJ0dbbfcgBqP9SCYq0VICN8xrtGN0wCffE6i kq1LlDwlJwmfrOtwRBwGqFg= =olf3 -----END PGP SIGNATURE-----