pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Jim C. Nasby <jnasby@pervasive.com>
To: Steve Crawford <scrawford@pinpointresearch.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: Archive Command Configuration
Date: Fri, 24 Mar 2006 05:42:22 -0600
Message-ID: <20060324114222.GV90527@pervasive.com> (raw)
In-Reply-To: <442304F9.4090708@pinpointresearch.com>
References: <4422FD80.5080009@livedatagroup.com>
	<442304F9.4090708@pinpointresearch.com>

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/
-- 
Jim C. Nasby, Sr. Engineering Consultant      jnasby@pervasive.com
Pervasive Software      http://pervasive.com    work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf       cell: 512-569-9461



view thread (9+ messages)  latest in thread

Message-ID: <20060324114222.GV90527@pervasive.com>
Permalink:  ../20060324114222.GV90527@pervasive.com/
Also on:    postgresql.org/message-id/20060324114222.GV90527@pervasive.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: jnasby@pervasive.com, scrawford@pinpointresearch.com
  Subject: Re: Archive Command Configuration
  In-Reply-To: <20060324114222.GV90527@pervasive.com>
  References: <4422FD80.5080009@livedatagroup.com> <442304F9.4090708@pinpointresearch.com> <20060324114222.GV90527@pervasive.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox