pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Pallav Kalva <pkalva@livedatagroup.com>
To: pgsql-admin@postgresql.org
Subject: Archive Command Configuration
Date: Thu, 23 Mar 2006 14:56:48 -0500
Message-ID: <4422FD80.5080009@livedatagroup.com> (raw)

Hi,


    I am in the process of implementing Failover to our production 
database. Inorder to able to restore to the last archive log, I have 
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. )


  With this command the archive log files are first copied to a 
temporary location and then moved over to the actual location to which I 
can point my cron job and do the scp to remote location every 5-10 min.
   I tried with this command on a test machine and made sure that the 
logs are moved over from archive-temp to archives directory, it works.


  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 ?

  postgresql version is 8.0.2.

Thanks!
Pallav.



view thread (9+ messages)  latest in thread

Message-ID: <4422FD80.5080009@livedatagroup.com>
Permalink:  ../4422FD80.5080009@livedatagroup.com/
Also on:    postgresql.org/message-id/4422FD80.5080009@livedatagroup.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: pkalva@livedatagroup.com
  Subject: Re: Archive Command Configuration
  In-Reply-To: <4422FD80.5080009@livedatagroup.com>
  References: <4422FD80.5080009@livedatagroup.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