Received: from maia.hub.org (maia-5.hub.org [200.46.204.29]) by mail.postgresql.org (Postfix) with ESMTP id E7862632AF0 for ; Fri, 16 Jul 2010 10:07:15 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.29]) (amavisd-maia, port 10024) with ESMTP id 78010-07 for ; Fri, 16 Jul 2010 13:07:08 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from lo.gmane.org (lo.gmane.org [80.91.229.12]) by mail.postgresql.org (Postfix) with ESMTP id 2ABEA6324F4 for ; Fri, 16 Jul 2010 10:07:07 -0300 (ADT) Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1OZkd7-0002XM-Er for pgsql-admin@postgresql.org; Fri, 16 Jul 2010 15:07:05 +0200 Received: from 217.110.94.67 ([217.110.94.67]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 16 Jul 2010 15:07:05 +0200 Received: from spam_eater by 217.110.94.67 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 16 Jul 2010 15:07:05 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: pgsql-admin@postgresql.org From: Thomas Kellerer Subject: Re: Setting up a warm standby server - some questions Date: Fri, 16 Jul 2010 15:06:56 +0200 Lines: 51 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Complaints-To: usenet@dough.gmane.org X-Gmane-NNTP-Posting-Host: 217.110.94.67 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.23) Gecko/20090812 Thunderbird/2.0.0.23 Mnenhy/0.7.6.666 In-Reply-To: X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=1.153 tagged_above=-10 required=5 tests=BAYES_40=-0.001, RCVD_NUMERIC_HELO=1.164, T_RP_MATCHES_RCVD=-0.01 X-Spam-Level: * X-Archive-Number: 201007/106 X-Sequence-Number: 35125 Hello, I could solve one of the questions myself :) > I have also problems shutting down the secondary server while it is in > "standby" (i.e. recovery) mode This works fine when using "-m fast" instead of "-m immediate". I would still like an answer on these questions: > What is the recommended way to switch back to the primary, once that is > up and running again? > What is the recommended way to get the secondary back into the "standby" > mode? As we are trying to minimize the possible data loss, I'm looking at the archive_timeout setting (I'm currently evaluating our possibilities with 8.4) The manual at http://www.postgresql.org/docs/current/static/continuous-archiving.html#RECOVERY-CONFIG-SETTINGS states: "It is therefore unwise to set a very short archive_timeout — it will bloat your archive storage. archive_timeout settings of a minute or so are usually reasonable" But on the other hand http://www.postgresql.org/docs/current/static/warm-standby.html states: "The length of the window of data loss can be limited by use of the archive_timeout parameter, which can be set as low as a few seconds if required" but kind of restrains itself right after that by stating: "However such low settings will substantially increase the bandwidth requirements for file shipping" My question is: is that the bandwidth between primary and standby? If the archive is stored on a differend harddisk (or storgae system) as the data directory, I'd reckon it wouldn't have much impact on the primary server. Or am I missing something? Regards Thomas