Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 4EA642E0048 for ; Wed, 27 Feb 2008 17:12:32 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 61954-02 for ; Wed, 27 Feb 2008 17:12:29 -0400 (AST) X-Greylist: delayed 00:06:39.921783 by SQLgrey-1.7.5 Received: from livingmail01.inetu.net (unknown [209.235.247.80]) by postgresql.org (Postfix) with ESMTP id 1BB692E0045 for ; Wed, 27 Feb 2008 17:12:29 -0400 (AST) Received: (qmail 19173 invoked by uid 0); 27 Feb 2008 21:05:47 -0000 Received: from unknown (HELO ?192.168.0.23?) (salmanb@quietcaresystems.com@127.0.0.1) by livingmail01.inetu.net with SMTP; 27 Feb 2008 21:05:47 -0000 Message-ID: <47C5D0AB.7070102@quietcaresystems.com> Date: Wed, 27 Feb 2008 16:05:47 -0500 From: salman User-Agent: Mozilla-Thunderbird 2.0.0.6 (X11/20071009) MIME-Version: 1.0 To: libra dba CC: pgsql-admin@postgresql.org Subject: Re: Failover of the Primary database and starting the standby database in Postgresql in PITR configuraiton? References: <84D57263D486374587DA0820E60A2CC601B07E23@srit_mail.renaissance-it.com> <1203409158.16770.821.camel@ebony.site> <9abe84da0802190623o2a24f2a5u9a44299fd634618e@mail.gmail.com> <47BAFC47.4060902@quietcaresystems.com> <9abe84da0802200849w1f462558n270f4320a7465b6c@mail.gmail.com> <9abe84da0802271254j3a6463c8j7ccbe603bcdbf477@mail.gmail.com> In-Reply-To: <9abe84da0802271254j3a6463c8j7ccbe603bcdbf477@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200802/372 X-Sequence-Number: 28446 libra dba wrote: > continuing with the postgres replication using WARM STANDBY, what happens to > the wal_files which keeps on generating on the primary? > > Do we have to manually remove them or they are removed automatically, once > they have been recovered on the warm standby? > > Also a quick question, do we have to have a NFS for the wal_files, which > will be mounted on both the servers, or we can have folders on each server > and configure DRBD between them, so that whatever happens on one is copied > automatically on to the other. > > Thanks! > This is what I use -- may not be the best approach, but it has worked quite well for me so far: archive_command = 'gzip %p; rsync -av %p.gz -e \"ssh -p portNum -i /home/postgres/.ssh/id_dsa\" postgres@rhostname:/usr/local/postgresql/archives/recovery/%f.gz && rm -f %p.gz'