Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.92) (envelope-from ) id 1jBEvh-0003PM-34 for pgsql-hackers@arkaria.postgresql.org; Mon, 09 Mar 2020 09:42:33 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1jBEvf-0004iu-M4 for pgsql-hackers@arkaria.postgresql.org; Mon, 09 Mar 2020 09:42:31 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1jBEvf-0004im-Cb for pgsql-hackers@lists.postgresql.org; Mon, 09 Mar 2020 09:42:31 +0000 Received: from wout1-smtp.messagingengine.com ([64.147.123.24]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jBEvb-0001b4-NB for pgsql-hackers@postgresql.org; Mon, 09 Mar 2020 09:42:30 +0000 Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.west.internal (Postfix) with ESMTP id 7894A438; Mon, 9 Mar 2020 05:42:23 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Mon, 09 Mar 2020 05:42:23 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=AFCs/u72LeaZe2HODfVrlZELBXwYgz5eEoQJ8LZf8 BU=; b=FroI2sF4C4RVcT2M9t9lbMyW5dJT5YPipccYq4TgDEQENze89yFQ58tzS 4CzaMaNztjyzkPknP9QZcNDt5GrIJGtWPwkBOo7ecyhxKYY8mCi7tv/2bpLvQSI/ vE3JCtmMm3hs1MfQe4Fh9opYYNC7lcYX3SpLH5SskfOznwvC2SQfZv+jMSXODYVb oV7k27dyRxq82RjuL9efbktna3tOqgWtW/E0NP/3M3BlbB98vx/QWHoaEj8UKXo5 gkSsHneOa6xn2csaNw19Eg54b4M1ER0dabPO1uwdTlDrVZ3tInEUuMWrRgexKS39 YqAE0Iyd/Vll0XY76fGYPssKMmtPA== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedugedruddukedgtdekucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepuffvfhfhohfkffgfgggjtgfgsehtjeertddtfeejnecuhfhrohhmpefrvght vghrucfgihhsvghnthhrrghuthcuoehpvghtvghrrdgvihhsvghnthhrrghuthesvdhnug hquhgrughrrghnthdrtghomheqnecuffhomhgrihhnpedvnhguqhhurggurhgrnhhtrdgt ohhmnecukfhppeelfedrvdegvddrvddufedrvdegudenucevlhhushhtvghrufhiiigvpe dtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehpvghtvghrrdgvihhsvghnthhrrghuthes vdhnughquhgrughrrghnthdrtghomh X-ME-Proxy: Received: from april.pezone.net (p5df2d5f1.dip0.t-ipconnect.de [93.242.213.241]) by mail.messagingengine.com (Postfix) with ESMTPA id 3E1A53280066; Mon, 9 Mar 2020 05:42:22 -0400 (EDT) Subject: Re: Improve handling of parameter differences in physical replication To: Alvaro Herrera References: <20200228153331.GA31634@alvherre.pgsql> Cc: pgsql-hackers From: Peter Eisentraut Organization: 2ndQuadrant Message-ID: Date: Mon, 9 Mar 2020 10:42:21 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: <20200228153331.GA31634@alvherre.pgsql> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On 2020-02-28 16:33, Alvaro Herrera wrote: > Hmm, so what is the actual end-user behavior? As I read the code, we > first send the WARNING, then pause recovery until the user resumes > replication; at that point we raise the original error. Presumably, at > that point the startup process terminates and is relaunched, and replay > continues normally. Is that it? No, at that point you get the original, current behavior that the server instance shuts down with a fatal error. -- Peter Eisentraut http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services