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 D5EE511F6646 for ; Wed, 29 Mar 2006 08:58:55 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 21290-07 for ; Wed, 29 Mar 2006 08:58:55 -0400 (AST) X-Greylist: domain auto-whitelisted by SQLgrey- Received: from nproxy.gmail.com (nproxy.gmail.com [64.233.182.190]) by postgresql.org (Postfix) with ESMTP id A235311F6623 for ; Wed, 29 Mar 2006 08:58:53 -0400 (AST) Received: by nproxy.gmail.com with SMTP id g2so126340nfe for ; Wed, 29 Mar 2006 04:58:53 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=SCSq3uPze+gWBfIwPbvuxjqD+FOvaP09CsfPk2J+qZjfB5e6ZiBXeNIH9UuECHFfJB82ooBb6vwPrm2A2EOqIyAM3IXXCH9AtP02QOwgUHmTAEWR4R/1TznIy/VWKrYgvh/8hMgXg9LkDjjEg5z5Jx73fJGb558qenscxNERfLE= Received: by 10.48.255.9 with SMTP id c9mr56921nfi; Wed, 29 Mar 2006 04:58:52 -0800 (PST) Received: by 10.49.26.20 with HTTP; Wed, 29 Mar 2006 04:58:51 -0800 (PST) Message-ID: Date: Wed, 29 Mar 2006 18:28:51 +0530 From: "Rajesh Kumar Mallah" To: andy.shellam@mailnetwork.co.uk Subject: Re: FW: Setting up of PITR system. Cc: pgsql-admin@postgresql.org In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.708 required=5 tests=[AWL=0.708] X-Spam-Score: 0.708 X-Spam-Level: X-Archive-Number: 200603/339 X-Sequence-Number: 21096 On 3/29/06, Andy Shellam wrote: > If pg_start_backup is used correctly, no data pages will be written to di= sk > until pg_stop_backup is called, so this shouldn't be an issue - HOWEVER - > check that you're excluding your pg_xlog directory (within your database > directory) from the tar backup as these will be changing. > > Whatever archive utility you're using, if a file is being changed at the > time of reading, it won't be archived correctly. ?????? What you are saying is not in sync with docs >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 23.3.2. Making a Base Backup The procedure for making a base backup is relatively simple: 3. Perform the backup, using any convenient file-system-backup tool such as tar or cpio. It is neither necessary nor desirable to stop normal operation of the database while you do this. >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> I used rsync like many others , it seems to work fine for me. Regds mallah. > > Andy > > -----Original Message----- > From: pgsql-admin-owner@postgresql.org > [mailto:pgsql-admin-owner@postgresql.org] On Behalf Of Rajesh Kumar Malla= h > Sent: Tuesday, 28 March, 2006 5:27 PM > To: Tom Lane > Cc: andy.shellam@mailnetwork.co.uk; pgsql-admin@postgresql.org > Subject: Re: FW: [ADMIN] Setting up of PITR system. > > --- > > secondly , i was asking about the tool for copying the > database directory not the one for archiving the logs. > when i use tar , it gives warning that the file changed > while it was reading the file, i need a tool that does not > give warning for this kind of activity. > > --- > > >