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 1kYLn0-0006JL-Q4 for pgsql-bugs@arkaria.postgresql.org; Fri, 30 Oct 2020 04:13:23 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1kYLmy-0006RP-Sd for pgsql-bugs@arkaria.postgresql.org; Fri, 30 Oct 2020 04:13:20 +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 1kYLmx-0006Pa-6s for pgsql-bugs@lists.postgresql.org; Fri, 30 Oct 2020 04:13:20 +0000 Received: from out3-smtp.messagingengine.com ([66.111.4.27]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kYLmt-0004CM-DT for pgsql-bugs@lists.postgresql.org; Fri, 30 Oct 2020 04:13:18 +0000 Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 144795C008C; Fri, 30 Oct 2020 00:13:12 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Fri, 30 Oct 2020 00:13:12 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=paquier.xyz; h= date:from:to:cc:subject:message-id:references:mime-version :content-type:in-reply-to; s=fm3; bh=0N29V7c1g22fBP+Zo9toUyLezpk /mosjMLTuDNY0Dxc=; b=pYdzA9BZCaeHajjPuNPA1CRzZWgP7Str1OT1xNDOzXB r6Eo1891NeU6ZfoiCBN7ATXdS/WtH20McvX/1vJ3KkxX6zUmNxR/OgGOyPkLCXqG t5reMcAuhcWho1zyV9YGk5rqYGcp4ak0xlSHcyeCSH9okBgo5+MPrGDSwih0BO6L KjdfULe4nFDa2Dov/Q49ffjA7VsTA+vUdMhLZlpPKV6PcSlIHL/iVVG52oUYE6IB qruP3euKg3CMD7i7c6dSrXTZYr9LDDrfe2+vlUA2QfkqteqV1dE9CgL6pb6+MFgH +OfDwEPD07wC0z/IvrzBXBNozIReQ7R0ryjef1ZwtPA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc: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=fm1; bh=0N29V7 c1g22fBP+Zo9toUyLezpk/mosjMLTuDNY0Dxc=; b=ITId+WdlS6/bQwNWK45nRS uVRsaSfpIaaLYfPo3CJd60tY22Jk5BNpb3EuBD3/fDFO4KK70SZH7s0hS3gBa1tJ 2x/znHPpcnUCGofY9n3YAAX2m1wkRcRahV8bIX/loh7CIwmBaJLDmvvu6zE0asIB F4eQcmGLiPEHD5RHiUYynJflWAUxNS8+/oeMnwcSPoPXS04jG9zKJH1KXvaVqVmr ICPmw8Rcdw2St6wSQuyb9W6KwO5IGov7dUyL7BSOjRCWJKwT3voCYLW597LlZxJO IAvz2SUYad2+1oNVw8e8yTWK+sx/SwYOM5MF2EdqVdODAK7kE3Y9R/QosyX8E9jA == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedujedrleeggdeijecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenfg hrlhcuvffnffculdefhedmnecujfgurhepfffhvffukfhfgggtuggjsehgtderredttddv necuhfhrohhmpefoihgthhgrvghlucfrrghquhhivghruceomhhitghhrggvlhesphgrqh huihgvrhdrgiihiieqnecuggftrfgrthhtvghrnhepvdegudeuhfdtueeltedtveejheeh ieevueeigeelteegleejleeiueeiheegvefhnecukfhppeduuddurddutddvrddukedtrd dukeehnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhep mhhitghhrggvlhesphgrqhhuihgvrhdrgiihii X-ME-Proxy: Received: from paquier.xyz (ee0822lan1.rev.em-net.ne.jp [111.102.180.185]) by mail.messagingengine.com (Postfix) with ESMTPA id E21A93280063; Fri, 30 Oct 2020 00:13:09 -0400 (EDT) Date: Fri, 30 Oct 2020 13:13:06 +0900 From: Michael Paquier To: Tom Lane Cc: Alvaro Herrera , Tomas Vondra , exclusion@gmail.com, pgsql-bugs@lists.postgresql.org Subject: Re: BUG #16577: Segfault on altering a table located in a dropped tablespace Message-ID: <20201030041306.GF1693@paquier.xyz> References: <20201028134045.GA6709@alvherre.pgsql> <1251838.1603893564@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="zGQnqpIoxlsbsOfg" Content-Disposition: inline In-Reply-To: <1251838.1603893564@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --zGQnqpIoxlsbsOfg Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Wed, Oct 28, 2020 at 09:59:24AM -0400, Tom Lane wrote: > Alvaro Herrera writes: >> I haven't started on this one yet, but I intend to do so shortly. Cool. Glad to hear that. >> Strictly speaking, we can still introduce a new category of pg_shdepend >> entries in back branches; it won't break anything that works today. > > Yeah, as long as the patched version won't actively fail when those > pg_shdepend entries are missing, I don't think a backpatch is too > hazardous. It might be worth checking that the extra entries don't > create huge problems if one does downgrade after some of them exist > --- but my feeling for how that mechanism works is that it'd Just > Work, and indeed provide the missing DROP protection even without > explicit action by the backend. Good point. Even with that, we have never considered the case of a downgrade as something actually supported, right? We had in the past for example bug fixes that involve slight tweaks in the WAL records that are upward-compatible, changing the way these get interpreted when replayed, but it could be possible to finish with logical corruptions or replay failures if a downgraded version replays a slightly-modified record generated by a newer version, no? -- Michael --zGQnqpIoxlsbsOfg Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEG72nH6vTowiyblFKnvQgOdbyQH0FAl+bktIACgkQnvQgOdby QH3SVg/+Nw5hyedURxR3Ldf0VDiC/BQnzyc/10F2OOLyV8gdsAN/zMNSSXu+mF6V KVK21C4eZIh+JDfPMA2xVa6d7OsTCl6pKnKHN57v+t00PmT9z9nQ04Qj126XzJWy 7ZHExYW4tWt4zevGz2KSbZhzh9QsJfAiQUd8t8FinYJXcwF/aYQjyicwSeFxpWI8 nogcd+wVkMZ0r6iCxxbGukfYs9mQgU8mpjIcU7VJCkDpk2WCIuu2MCYx8BmyCw+B GKj7jhwSWOHPTTwUpy1BgVR9isCYb9dNjiTQLlnAAEqFW6QKDhiJchoEpr7UVNOb W/lw6tYFKbkSw373meXd/itKtms+9d9UCCH0R+vlnrV8r9ILixR1JHtQAqkjG5rT RKwzpAsyICJKe8w/AxGZx9QAfzUU5xKy/QuwqsRNIF1Vt2QWRcFJCnNwCuJckyrt avwocylX1G3IhL3ZRdmFseQJJovf43u4azP+Qp5vBxqcuxHwpUq2xU6RRBME+xhC tqx08hzC1C1gb8eL9lcPwDvDXmsns//xYTCrprXo+ruWzDA+ukUcUjWYs6qibQcV rsUEh1TnExxXVsQkO7PkNTacAOs4PvXJP4Bz51rXjtskfTI0LvPC0L2VaFe4N4Rv IY5VJ4mAyGcS5Vod2xAnRkX9CuUpmGlONPwLZQdp7S+sZKR+S/4= =hYGm -----END PGP SIGNATURE----- --zGQnqpIoxlsbsOfg--