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 1jWyC4-00068e-OF for pgsql-hackers@arkaria.postgresql.org; Fri, 08 May 2020 08:17:17 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1jWyC3-0001Hs-Lh for pgsql-hackers@arkaria.postgresql.org; Fri, 08 May 2020 08:17:15 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jWyC2-0001Hl-MI for pgsql-hackers@lists.postgresql.org; Fri, 08 May 2020 08:17:15 +0000 Received: from wforward2-smtp.messagingengine.com ([64.147.123.31]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jWyBz-0000Yl-Qd for pgsql-hackers@postgresql.org; Fri, 08 May 2020 08:17:13 +0000 Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailforward.west.internal (Postfix) with ESMTP id CCCF38BA; Fri, 8 May 2020 04:17:09 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Fri, 08 May 2020 04:17:10 -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=JMjwcc8wYZn72n5Oi2u6fsb6LnDfNgKWV4rRh/Bsr V4=; b=wJtY1plyURur+aHoXnGUO8SHPBV4rrIdEScGuHqEAIZgJbiE+1p2mu3KN ir8UVR6aw+WiHsUSyuII4vlrvloMNVXbsaHgBESqP7gL3UOOzJiZbLlwTTwULDk+ v7FItNGFJwMqaRl1g8zSH5PXcQ+kJ2JgprUJzkFIM/bvqFQg4YYSBOnSwjrzpQ/w yhCGEXG3Pr5LnFhKwnAe7BJT3Uy4rP/FMTlRjUyQn1qEls1I/3PNEViKbxNH8h8U PaeTH7qCp6wYPGrDrUerbAPLWAANBK4UbjTXVeN4AVeJkhHLx62RSkheqpJw9bqQ Dg2hpbKuyUW/FktAvzrDQL/dKvi3A== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduhedrkedvgddtudcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefuhffvfhhokffffgggjggtgfesthejredttdefjeenucfhrhhomheprfgvthgv rhcugfhishgvnhhtrhgruhhtuceophgvthgvrhdrvghishgvnhhtrhgruhhtsedvnhguqh hurggurhgrnhhtrdgtohhmqeenucggtffrrghtthgvrhhnpedtheefgfdvudffudefvdej fedukeegudevjeevhfduudekuefhvdevueejfedvteenucffohhmrghinhepvdhnughquh grughrrghnthdrtghomhenucfkphepleefrddvgeefrddufedvrdekudenucevlhhushht vghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehpvghtvghrrdgvihhsvg hnthhrrghuthesvdhnughquhgrughrrghnthdrtghomh X-ME-Proxy: Received: from april.pezone.net (p5df38451.dip0.t-ipconnect.de [93.243.132.81]) by mail.messagingengine.com (Postfix) with ESMTPA id 8AE6F30661F0; Fri, 8 May 2020 04:17:08 -0400 (EDT) Subject: Re: ALTER TABLE ... SET STORAGE does not propagate to indexes From: Peter Eisentraut To: Alvaro Herrera References: <20200421235636.GA29434@alvherre.pgsql> <8be09419-ed3d-93f9-9c29-2824b44a2c56@2ndquadrant.com> <1e19aeb2-c300-a8a0-e828-9090671eb428@2ndquadrant.com> Cc: Kuntal Ghosh , pgsql-hackers Organization: 2ndQuadrant Message-ID: Date: Fri, 8 May 2020 10:17:07 +0200 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: <1e19aeb2-c300-a8a0-e828-9090671eb428@2ndquadrant.com> 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-05-06 16:37, Peter Eisentraut wrote: > On 2020-04-22 16:26, Peter Eisentraut wrote: >> On 2020-04-22 01:56, Alvaro Herrera wrote: >>> I'm surprised that this hasn't applied yet, because: >>> >>> On 2020-Apr-09, Peter Eisentraut wrote: >>> >>>> One thing to remember is that the current situation is broken. While you >>>> can set index columns to have different storage than the corresponding table >>>> columns, pg_dump does not preserve that, because it dumps indexes after >>>> ALTER TABLE commands. So at the moment, having these two things different >>>> isn't really supported. >>> >>> So I have to ask -- are you planning to get this patch pushed and >>> backpatched? >> >> I think I should, but I figured I want to give some extra time for >> people to consider the horror that I created in the test_decoding tests. > > OK then, if there are no last-minute objects, I'll commit this for the > upcoming minor releases. I have committed this and backpatched to PG12 and PG11. Before that, the catalog manipulation code is factored quite differently and it would be more complicated to backpatch and I didn't find that worth it. -- Peter Eisentraut http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services