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 1l2Fhf-000470-Fo for pgsql-hackers@arkaria.postgresql.org; Wed, 20 Jan 2021 15:47:27 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1l2Fhe-0004Hy-Da for pgsql-hackers@arkaria.postgresql.org; Wed, 20 Jan 2021 15:47:26 +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 1l2Fhd-0004Hk-CY for pgsql-hackers@lists.postgresql.org; Wed, 20 Jan 2021 15:47:26 +0000 Received: from [66.111.4.221] (helo=new1-smtp.messagingengine.com) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1l2Fha-0006KA-U5 for pgsql-hackers@lists.postgresql.org; Wed, 20 Jan 2021 15:47:24 +0000 Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailnew.nyi.internal (Postfix) with ESMTP id 91603580534; Wed, 20 Jan 2021 10:47:11 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute2.internal (MEProxy); Wed, 20 Jan 2021 10:47:11 -0500 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=AKXRyRzrFN58zNlhhRNIriNMGC8WMbLrjgtyuHB1FWI=; b=m8vOBj10 T5qdY6NmiyW821rCcDaPhSHZ2WriY72rv3m2I+B5Xxg/BicFjhyPE+a/vDpsJoad LtIs8OdEWFGC5xkwqUXrUZLaRRODCcLrDqdcZR03mlU4mThYD8qURoth7ekB+pCJ NG0i4e68ioEBZVvCaxc5oCwk3skgKvvA4f+eO0DnrKVrX3yI5pZaiOzwMwg4M32c ql3px0qboDEOayDqha8XDfJT+TvFXmBcRSXr5UTzbeutlF6jgIR2nFAiISGtvQZk 0ZzN49aljXhLiSpLVpC0GjnEyj/S1N/8JX+vsP+vfQWplLu/41tf9DB4nirY46zV XYmIP4bUuwZiHg== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledruddvgdekudcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpeffhffvuffkgggtugfgjggfsehtkeertddtredunecuhfhrohhmpeetlhhvrghr ohcujfgvrhhrvghrrgcuoegrlhhvhhgvrhhrvgesrghlvhhhrdhnohdqihhprdhorhhgqe enucggtffrrghtthgvrhhnpeeufffhjeeiueeuffegvddukeegledtveeivdeiueefieei vefgteehueefteehvdenucfkphepudeltddrleehrdduledrudejjeenucevlhhushhtvg hrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpegrlhhvhhgvrhhrvgesrghl vhhhrdhnohdqihhprdhorhhg X-ME-Proxy: Received: from perhan.alvh.no-ip.org (unknown [190.95.19.177]) by mail.messagingengine.com (Postfix) with ESMTPA id ED0B0108005B; Wed, 20 Jan 2021 10:47:09 -0500 (EST) Received: by perhan.alvh.no-ip.org (Postfix, from userid 1000) id ACCFF2A0FBF; Wed, 20 Jan 2021 12:47:07 -0300 (-03) Date: Wed, 20 Jan 2021 12:47:07 -0300 From: Alvaro Herrera To: Michael Paquier Cc: Justin Pryzby , Peter Eisentraut , Alexey Kondratov , Masahiko Sawada , Steve Singer , pgsql-hackers@lists.postgresql.org, Robert Haas , Alexander Korotkov , Masahiko Sawada , Jose Luis Tallon Subject: Re: Allow CLUSTER, VACUUM FULL and REINDEX to change tablespace on the fly Message-ID: <20210120154707.GA9324@alvherre.pgsql> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) X-Host-Lookup-Failed: Reverse DNS lookup failed for 66.111.4.221 (deferred) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On 2021-Jan-20, Michael Paquier wrote: > +/* > + * This is mostly duplicating ATExecSetTableSpaceNoStorage, > + * which should maybe be factored out to a library function. > + */ > Wouldn't it be better to do first the refactoring of 0002 and then > 0001 so as REINDEX can use the new routine, instead of putting that > into a comment? I think merging 0001 and 0002 into a single commit is a reasonable approach. I don't oppose an initial refactoring commit if you want to do that, but it doesn't seem necessary. -- Álvaro Herrera 39°49'30"S 73°17'W