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 1oEUIr-0002HV-Nm for pgsql-hackers@arkaria.postgresql.org; Thu, 21 Jul 2022 11:25:13 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1oEUIq-0005pO-87 for pgsql-hackers@arkaria.postgresql.org; Thu, 21 Jul 2022 11:25:12 +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 1oEUIp-0005pF-Um for pgsql-hackers@lists.postgresql.org; Thu, 21 Jul 2022 11:25:11 +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 1oEUIn-0001XZ-Au for pgsql-hackers@postgresql.org; Thu, 21 Jul 2022 11:25:11 +0000 Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 38AB15C0152; Thu, 21 Jul 2022 07:25:08 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Thu, 21 Jul 2022 07:25:08 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:date:date:feedback-id:feedback-id:from:from :in-reply-to:in-reply-to:message-id:mime-version:reply-to:sender :subject:subject:to:to:x-me-proxy:x-me-proxy:x-me-sender :x-me-sender:x-sasl-enc; s=fm3; t=1658402708; x=1658489108; bh=o BMEyjHX5I3QTCAxdRusvYGo98AiSrH0w7FPnlvs0KM=; b=LcG4iOgPRSYifgdCl sAFp/R91l1utbP3bD8qqxOt+I4hDiQyZ4P4H8cNs/kK5EfE7eL+dWDD5V2vQzqZh B+AIo8qQqo/+A8XYQWXetSDmGaBPhH5D1+uO8MB6wrVuKXWW1zgv0RD/yc7ZA/5R RKLjnmIdqozbdc4bY/Nssk8MMR+tN+CXG6iygQeO7Tem2fVsBJeJYHbur5gYGNSR dCkCL0vEpzCDoW5htVJqrALTbdGOViEC2w2WfwKyfUQbIsfaxxTZD13qls9h+yso c9uapEIDXMXMDmNK/Vq/rTiCgczkPeS6HVDAnqjDT2xUj5ZJT9to/Gfdz+CC1l8Y ioWaQ== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvfedrudelledggeduucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepfffhvfevuffkgggtugfgjgesthekredttddtjeenucfhrhhomheptehlvhgr rhhoucfjvghrrhgvrhgruceorghlvhhhvghrrhgvsegrlhhvhhdrnhhoqdhiphdrohhrgh eqnecuggftrfgrthhtvghrnhepvdektdffudfftdffffehfffhjeejhffgieeuueekjeek fffgudffhfduffffueevnecuffhomhgrihhnpegvnhhtvghrphhrihhsvggusgdrtghomh enucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpegrlhhv hhgvrhhrvgesrghlvhhhrdhnohdqihhprdhorhhg X-ME-Proxy: Feedback-ID: ia2694551:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Thu, 21 Jul 2022 07:25:07 -0400 (EDT) Received: by perhan.alvh.no-ip.org (Postfix, from userid 1000) id 07FC5369; Thu, 21 Jul 2022 13:25:05 +0200 (CEST) Date: Thu, 21 Jul 2022 13:25:05 +0200 From: Alvaro Herrera To: Thomas Munro Cc: Kyotaro Horiguchi , Dilip Kumar , Robert Haas , Michael Paquier , Julien Rouhaud , pgsql-hackers Subject: Re: standby recovery fails (tablespace related) (tentative patch and discussion) Message-ID: <20220721112505.ox2nrinutis3eubn@alvherre.pgsql> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20220721112026.xvqhrhtvsev47keo@alvherre.pgsql> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 2022-Jul-21, Alvaro Herrera wrote: > Yeah, I think that would reduce cruft. I'm not sure this is more > against backpatching policy or less, compared to adding a separate > GUC just for this bugfix. cruft: { {"allow_recovery_tablespaces", PG_POSTMASTER, WAL_RECOVERY, gettext_noop("Continues recovery after finding invalid database directories."), gettext_noop("It is possible for tablespace drop to interfere with database creation " "so that WAL replay is forced to create fake database directories. " "These should have been dropped by the time recovery ends; " "but in case they aren't, this option lets recovery continue if they " "are present. Note that these directories must be removed manually afterwards."), GUC_NOT_IN_SAMPLE }, &allow_recovery_tablespaces, false, NULL, NULL, NULL }, This is not a very good explanation, but I don't know how to make it better. -- Álvaro Herrera PostgreSQL Developer — https://www.EnterpriseDB.com/ "I think my standards have lowered enough that now I think 'good design' is when the page doesn't irritate the living f*ck out of me." (JWZ)