Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1YSUkh-0000Hw-Ep for pgsql-hackers@arkaria.postgresql.org; Mon, 02 Mar 2015 18:07:35 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1YSUkg-0002eS-Sz for pgsql-hackers@arkaria.postgresql.org; Mon, 02 Mar 2015 18:07:34 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1YSUkf-0002cG-K6 for pgsql-hackers@postgresql.org; Mon, 02 Mar 2015 18:07:33 +0000 Received: from mx-out.zmailcloud.com ([192.198.85.98] helo=mx-out-1.zmailcloud.com) by magus.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1YSUkb-0003mO-Mq for pgsql-hackers@postgresql.org; Mon, 02 Mar 2015 18:07:32 +0000 Received: from smtp.01.com (smtp.01.com [10.10.0.43]) by mx-out-1.zmailcloud.com (Postfix) with ESMTP id 08084563DF0; Mon, 2 Mar 2015 12:07:29 -0600 (CST) Received: from localhost (localhost [127.0.0.1]) by smtp-out-2.01.com (Postfix) with ESMTP id F1D786021E; Mon, 2 Mar 2015 12:07:28 -0600 (CST) X-Virus-Scanned: amavisd-new at smtp-out-2.01.com Received: from smtp.01.com ([127.0.0.1]) by localhost (smtp-out-2.01.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Luix0SbFEgd0; Mon, 2 Mar 2015 12:07:28 -0600 (CST) Received: from smtp.01.com (localhost [127.0.0.1]) by smtp-out-2.01.com (Postfix) with ESMTP id CF9DC60219; Mon, 2 Mar 2015 12:07:28 -0600 (CST) Received: from localhost (localhost [127.0.0.1]) by smtp-out-2.01.com (Postfix) with ESMTP id B7E8E6021E; Mon, 2 Mar 2015 12:07:28 -0600 (CST) X-Virus-Scanned: amavisd-new at smtp-out-2.01.com Received: from smtp.01.com ([127.0.0.1]) by localhost (smtp-out-2.01.com [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id 7-D2YkZhbZJe; Mon, 2 Mar 2015 12:07:28 -0600 (CST) Received: from [172.47.23.102] (50-0-89-53.dsl.dynamic.fusionbroadband.com [50.0.89.53]) by smtp-out-2.01.com (Postfix) with ESMTPSA id 2D74A60219; Mon, 2 Mar 2015 12:07:28 -0600 (CST) Message-ID: <54F4A6DF.1090808@agliodbs.com> Date: Mon, 02 Mar 2015 10:07:27 -0800 From: Josh Berkus Organization: PostgreSQL Experts Inc. User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: Fujii Masao , hlinnaka@iki.fi CC: PostgreSQL-development Subject: Re: remove pg_standby? References: <545946E9.8060504@gmx.net> <5460FAFF.2000805@commandprompt.com> <5461087E.6090003@vmware.com> <54F0CCE3.7080507@agliodbs.com> <54F44B93.401@iki.fi> In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Pg-Spam-Score: -1.9 (-) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-hackers Precedence: bulk Sender: pgsql-hackers-owner@postgresql.org > Per document, > > ------------------ > In fast failover, the server is brought up immediately. Any WAL files > in the archive that have not yet been applied will be ignored, and all > transactions in those files are lost. To trigger a fast failover, > create a trigger file and write the word fast into it. pg_standby can > also be configured to execute a fast failover automatically if no new > WAL file appears within a defined interval. > ------------------ I thought we had that as a 9.4 feature, actually. Well wait ... that's for streaming. -- Josh Berkus PostgreSQL Experts Inc. http://pgexperts.com -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers