Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mixzx-0007Ug-2Z for pgsql-hackers@arkaria.postgresql.org; Fri, 05 Nov 2021 12:07:09 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1mixzv-0005Qd-T3 for pgsql-hackers@arkaria.postgresql.org; Fri, 05 Nov 2021 12:07:07 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mixzv-0005QU-1d for pgsql-hackers@lists.postgresql.org; Fri, 05 Nov 2021 12:07:07 +0000 Received: from out3-smtp.messagingengine.com ([66.111.4.27]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mixzm-0007fK-MD for pgsql-hackers@lists.postgresql.org; Fri, 05 Nov 2021 12:07:06 +0000 Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.nyi.internal (Postfix) with ESMTP id 1546F5C00B8; Fri, 5 Nov 2021 08:06:55 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute5.internal (MEProxy); Fri, 05 Nov 2021 08:06:55 -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:subject:to :x-me-proxy:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s= fm1; bh=F4gyKhVzWHRArBPB69Zu8NwlOp3adxhFfAmZX6u9Qm4=; b=JlQOh7iJ Zj1L7DlWUbbiCOL3AI19+xerR9gjCw8iQ1hRyFHe8SdGBwF/6y2fE1UoOIajP/3P LKIs3kI9hEAL8aV1jwGzTNz7J1Wi+rTSwtvhubjv4OixhzunVhTaoFTnPU6dyiNE zB95LdrLDlog61SGwItfbBhgHeOEeYQI8dnefQz/GOBj5N6y9P4WVh5K2HLHMhws zMD3pgfBGT9MFKAJY8P4hXMApKZcKQ/vIuXaVMBIDjMTAZWCaeWk1M4+za1igI+X OB2Kt9JeP4HXHbvPXIGyGr7DbEYYO9ntpzAMhTwb+VsFXp3EQave3nn8ePfMnY3w RXnA0UNGckyzOg== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvuddrtdeigdefhecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhepfffhvffukfggtggugfgjsehtkeertd dttdejnecuhfhrohhmpeetlhhvrghrohcujfgvrhhrvghrrgcuoegrlhhvhhgvrhhrvges rghlvhhhrdhnohdqihhprdhorhhgqeenucggtffrrghtthgvrhhnpedujeevjeffjeevud dutedvkeeiueeitddvieelfeekveejudefgeeuvdejhfeuleenucffohhmrghinhepvghn thgvrhhprhhishgvuggsrdgtohhmnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrg hmpehmrghilhhfrhhomheprghlvhhhvghrrhgvsegrlhhvhhdrnhhoqdhiphdrohhrgh X-ME-Proxy: Received: by mail.messagingengine.com (Postfix) with ESMTPA; Fri, 5 Nov 2021 08:06:54 -0400 (EDT) Received: by perhan.alvh.no-ip.org (Postfix, from userid 1000) id D98582A0804; Fri, 5 Nov 2021 09:06:50 -0300 (-03) Date: Fri, 5 Nov 2021 09:06:50 -0300 From: Alvaro Herrera To: Tom Lane Cc: pgsql-hackers@lists.postgresql.org Subject: Re: pgsql: Fix WAL replay in presence of an incomplete record Message-ID: <202111051206.tcvp24m6fxyr@alvherre.pgsql> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <364321.1636071230@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 2021-Nov-04, Tom Lane wrote: > Is there really any point in issuing such advice? IIUC, the standbys > would be unable to proceed anyway in case of a primary crash at the > wrong time, because an un-updated primary would send them inconsistent > WAL. If anything, it seems like it might be marginally better to > update the primary first, reducing the window for it to send WAL that > the standbys will *never* be able to handle. Then, if it crashes, at > least the WAL contains something the standbys can process once you > update them. Yes -- in production settings, it is better to be able to shut down the standbys in a scheduled manner, than find out after updating the primary that your standbys are suddenly inaccessible until you take the further action of updating them. -- Álvaro Herrera PostgreSQL Developer — https://www.EnterpriseDB.com/ Si no sabes adonde vas, es muy probable que acabes en otra parte.