Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1YRR5X-0000Wd-KS for pgsql-hackers@arkaria.postgresql.org; Fri, 27 Feb 2015 20:00:43 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1YRR5X-00069V-2y for pgsql-hackers@arkaria.postgresql.org; Fri, 27 Feb 2015 20:00:43 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1YRR5V-00069P-QN for pgsql-hackers@postgresql.org; Fri, 27 Feb 2015 20:00:41 +0000 Received: from mx-out.zmailcloud.com ([192.198.85.98] helo=mx-out-1.zmailcloud.com) by makus.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1YRR5S-00034C-2C for pgsql-hackers@postgresql.org; Fri, 27 Feb 2015 20:00:39 +0000 Received: from smtp.01.com (smtp.01.com [10.10.0.43]) by mx-out-1.zmailcloud.com (Postfix) with ESMTP id A218B563D5A for ; Fri, 27 Feb 2015 14:00:37 -0600 (CST) Received: from localhost (localhost [127.0.0.1]) by smtp-out-1.01.com (Postfix) with ESMTP id 9E317A04B2 for ; Fri, 27 Feb 2015 14:00:37 -0600 (CST) X-Virus-Scanned: amavisd-new at smtp-out-1.01.com Received: from smtp.01.com ([127.0.0.1]) by localhost (smtp-out-1.01.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8o9Nw3rzmoEE for ; Fri, 27 Feb 2015 14:00:37 -0600 (CST) Received: from smtp.01.com (localhost [127.0.0.1]) by smtp-out-1.01.com (Postfix) with ESMTP id 77F88A04E9 for ; Fri, 27 Feb 2015 14:00:37 -0600 (CST) Received: from localhost (localhost [127.0.0.1]) by smtp-out-1.01.com (Postfix) with ESMTP id 6B2B3A04E8 for ; Fri, 27 Feb 2015 14:00:37 -0600 (CST) X-Virus-Scanned: amavisd-new at smtp-out-1.01.com Received: from smtp.01.com ([127.0.0.1]) by localhost (smtp-out-1.01.com [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id IX21N-a-fUAp for ; Fri, 27 Feb 2015 14:00:37 -0600 (CST) Received: from [172.47.23.102] (50-0-89-53.dsl.dynamic.fusionbroadband.com [50.0.89.53]) by smtp-out-1.01.com (Postfix) with ESMTPSA id 06617A04B2 for ; Fri, 27 Feb 2015 14:00:36 -0600 (CST) Message-ID: <54F0CCE3.7080507@agliodbs.com> Date: Fri, 27 Feb 2015 12:00:35 -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: pgsql-hackers@postgresql.org Subject: Re: remove pg_standby? References: <545946E9.8060504@gmx.net> <5460FAFF.2000805@commandprompt.com> <5461087E.6090003@vmware.com> 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 On 11/10/2014 10:54 AM, Magnus Hagander wrote: > On Mon, Nov 10, 2014 at 7:48 PM, Heikki Linnakangas > wrote: >> pg_standby is more configurable than the built-in standby_mode=on. You can >> set the sleep time, for example, while standby_mode=on uses a hard-coded >> delay of 5 s. And pg_standby has a configurable maximum wait time. And as >> Fujii pointed out, the built-in system will print an annoying message to the >> log every time it attempts to restore a file. Nevertheless, 99% of users >> would probably be happy with the built-in thing. > > As long as pg_standby has features that are actually useful and that > are not in the built-in system, we shouldn't remove it. We should, > however, try to fix those in the main system so we can get rid of it > after that :) As of current 9.5, we have configurable retries and standby delay in mainstream. Is there some reason we still need pg_standby? -- 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