Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1eZOT2-0007pK-Qb for pgsql-admin@arkaria.postgresql.org; Wed, 10 Jan 2018 22:03:28 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1eZOT2-0003vo-Dl for pgsql-admin@arkaria.postgresql.org; Wed, 10 Jan 2018 22:03:28 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1eZOQR-0004YF-A3 for pgsql-admin@lists.postgresql.org; Wed, 10 Jan 2018 22:00:47 +0000 Received: from out3-smtp.messagingengine.com ([66.111.4.27]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1eZOQO-0006AX-KE for pgsql-admin@postgresql.org; Wed, 10 Jan 2018 22:00:46 +0000 Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id AE12F20B94; Wed, 10 Jan 2018 17:00:43 -0500 (EST) Received: from frontend1 ([10.202.2.160]) by compute7.internal (MEProxy); Wed, 10 Jan 2018 17:00:43 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=XDxEXk yutRVfk5OuXbqHsDLub72HT+mnGAeHDymW9cY=; b=LPIkl8P7LvqBfrythpPWA6 QfhLSPj5aSjTaJ3+p66OG1dSCYtVFN6v/sMK4dTKPTEyS00/CgMTmpDMF8RlL5Cb D19SPrl7Tuu9nOlO7AhCyoPBLBW19PXet7H706G9P7xbdAA188Gv/ZJVc7GEgt9z RDenBC/7E01KGWozoC5dNEsfnNQ3rMbmeVf4daPKTV+ol1CmZ/jeydaP/ehFX7SC NyMaw4EiWE0CuzyfbjVnJBR43mkuq+LqqJkGiIOWsD2k9DvS37OaDU3oRswb07dS kK2+MCRnbvhh6fIJVfMCLr5PgoWpOVv2+GRhivjQK7ytK/nTOHj82Kp+bwcRgXow == X-ME-Sender: Received: from april.local (c-73-13-66-39.hsd1.pa.comcast.net [73.13.66.39]) by mail.messagingengine.com (Postfix) with ESMTPA id 657EF7E353; Wed, 10 Jan 2018 17:00:43 -0500 (EST) Subject: Re: Replication mode To: Azimuddin Mohammed , pgsql-admin@postgresql.org References: From: Peter Eisentraut Organization: 2ndQuadrant Message-ID: Date: Wed, 10 Jan 2018 17:00:42 -0500 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On 1/10/18 15:24, Azimuddin Mohammed wrote: > May I know what is the core difference between HOT standby. Warm Stand by ? In PostgreSQL, "hot standby" is a mode for an instance in recovery that allows read-only commands to be executed on it. The term "warm standby" is not used by PostgreSQL, but you could think of a server in recovery that does not allow queries to be a warm standby, if you wish. -- Peter Eisentraut http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services