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 9BD3C9DC83F for ; Fri, 24 Mar 2006 11:39:40 -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 51750-04 for ; Fri, 24 Mar 2006 11:39:44 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey- Received: from mail.livedatagroup.com (unknown [64.139.144.2]) by postgresql.org (Postfix) with ESMTP id CF9489DC813 for ; Fri, 24 Mar 2006 11:39:37 -0400 (AST) Received: from [192.168.2.126] (adsl-074-228-048-194.sip.bct.bellsouth.net [74.228.48.194]) by mail.livedatagroup.com (Postfix) with ESMTP id 0055B55F8F; Fri, 24 Mar 2006 10:39:42 -0500 (EST) Message-ID: <442412BD.6090706@livedatagroup.com> Date: Fri, 24 Mar 2006 10:39:41 -0500 From: Pallav Kalva MIME-Version: 1.0 To: "Jim C. Nasby" Cc: Steve Crawford , pgsql-admin@postgresql.org Subject: Re: Archive Command Configuration References: <4422FD80.5080009@livedatagroup.com> <442304F9.4090708@pinpointresearch.com> <20060324114222.GV90527@pervasive.com> In-Reply-To: <20060324114222.GV90527@pervasive.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.12 required=5 tests=[AWL=0.120] X-Spam-Score: 0.12 X-Spam-Level: X-Archive-Number: 200603/237 X-Sequence-Number: 20994 Jim C. Nasby wrote: >On Thu, Mar 23, 2006 at 12:28:41PM -0800, Steve Crawford wrote: > >>>...I have a >>>cron job from the production database that runs every 5-10min to check >>>if there are any new archive logs and copy new archive logs to the >>>remote stand by failover machine. >>> >>>The problem with this scenario is that there might be a possibility that >>>I might scp a partially filled archive log over to the remote machine on >>>a heavily updated databases with batch jobs runnings most of the time >>>like ours. >>> >>> So, inorder to over come this we want to change the archive_command to >>> >>>archive_command = 'cp %p /archives-temp/%f && mv /archives-temp/%f >>>/archives/%f' >>>( I could do remote copy also with the command but I dont want to go >>>that route because of network problems. ) >>> >>>.... >>> >>>My question is there any problem in using this approach ? will I run >>>into problems in the future ? are there any other better ways of solving >>>this problem ? >>> >>Looks like it should work but have you considered using rsync instead? >>If the file grows from one pass to the next, rsync will send the >>differences. >> > >rsync does nothing to address the race condition issue, though. If you >fire up an rsync and the cp takes too long, you'll end up syncing a >partially written WAL file, which could potentially be bad. > >BTW, there's also now a project on pgFoundry for using PITR to keep a >warm-backup: http://pgfoundry.org/projects/pgpitrha/ > Hi Jim, What do you think about this option ? If I just do scp from the /archives folder, I will be ok and wont copy any partial files at any time right ? archive_command = 'cp %p /archives-temp/%f && mv /archives-temp/%f /archives/%f' Pallav.