Received: from maia.hub.org (unknown [200.46.208.211]) by mail.postgresql.org (Postfix) with ESMTP id 42C80633632 for ; Wed, 7 Apr 2010 14:48:10 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.208.211]) (amavisd-maia, port 10024) with ESMTP id 95141-07 for ; Wed, 7 Apr 2010 17:47:51 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.186]) by mail.postgresql.org (Postfix) with ESMTP id 150E96327E6 for ; Wed, 7 Apr 2010 14:47:10 -0300 (ADT) Received: from [192.168.0.105] (pool-96-244-14-10.bltmmd.fios.verizon.net [96.244.14.10]) by mrelayeu.kundenserver.de (node=mrbap0) with ESMTP (Nemesis) id 0Lx5o1-1NShRy3uwb-0179wb; Wed, 07 Apr 2010 19:47:08 +0200 Message-ID: <4BBCC51A.8090407@2ndquadrant.com> Date: Wed, 07 Apr 2010 13:47:06 -0400 From: Greg Smith User-Agent: Thunderbird 2.0.0.24 (X11/20100317) MIME-Version: 1.0 To: Renato Oliveira CC: pgsql-admin Subject: Re: turn pitr 'on' on PostgreSQL 8.2 - pg_standby References: <7965A9DCF12CC14984420BCC37B1608F25ABF310AB@Elzar.grant.co.uk> In-Reply-To: <7965A9DCF12CC14984420BCC37B1608F25ABF310AB@Elzar.grant.co.uk> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 8bit X-Provags-ID: V01U2FsdGVkX1/Mdyu5csc1qlr/nfSUpKN+TdTVOR/NxGOXYB1 zY5MNP+a2zrQFrZL770ch3R+J2k29+VDtF5nREYGv1U185THSL oLV/dmi+RidWvcTDaoOWK4ZcWb8EhHy X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.154 tagged_above=-10 required=5 tests=AWL=-0.969, BAYES_40=-0.185 X-Spam-Level: X-Archive-Number: 201004/70 X-Sequence-Number: 34164 Renato Oliveira wrote: > > What is the difference between: > > archive_command = on (is this command for 8.2?) > > |archive_mode = on (This one is for 8.3!)| > 8.2 doesn't have a archive_mode setting, that was added in 8.3. With 8.2, you set the archive_command in the same way as you do in 8.3. There just isn't a dedicated parameters to toggle archiving on and off that's separate from changing the command used. > |In order to bring the standby online I need a trigger file, something > like:| > > |can I call the trigger file whatever I want? for example; > ‘/var/log/postgres/postgresql.8.2.trigger’| > It doesn't matter where the trigger file is at so long as you use it correctly. The other thing to be careful of, that you already noted, is that since 8.2 doesn't ship with pg_standby, you need to grab your version of that. You should try to use the one that ships with 8.4. Also, it's not going to support the "%r" syntax in the restore_command, so you need to set the "-k" setting to a moderately high value for 8.2 servers. It's difficult to say exactly how high that must be for any possible workload. Something like "-k 256" is a reasonable starter setting that will save the last 4GB of archive logs shipped over on the standby, which is high enough to make deleting one of them prematurely unlikely (but not impossible for the right difficult workload). -- Greg Smith 2ndQuadrant US Baltimore, MD PostgreSQL Training, Services and Support greg@2ndQuadrant.com www.2ndQuadrant.us