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 1kl0hQ-0006gJ-EF for pgsql-admin@arkaria.postgresql.org; Fri, 04 Dec 2020 02:19:56 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1kl0hP-0004nW-4y for pgsql-admin@arkaria.postgresql.org; Fri, 04 Dec 2020 02:19:55 +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 1kl0hO-0004nO-TX for pgsql-admin@lists.postgresql.org; Fri, 04 Dec 2020 02:19:54 +0000 Received: from [64.147.123.20] (helo=wout4-smtp.messagingengine.com) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kl0hN-0002MZ-0Q for pgsql-admin@lists.postgresql.org; Fri, 04 Dec 2020 02:19:53 +0000 Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.west.internal (Postfix) with ESMTP id 4EDAEDD8; Thu, 3 Dec 2020 21:19:41 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute2.internal (MEProxy); Thu, 03 Dec 2020 21:19:41 -0500 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:subject:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=Rvu0GS6PRTTVOXWiZ YSVBFp4rCTVsN4pZnGwqiF8foQ=; b=LqO5Zs3XkmaRGBarRC4AIKSqWWZ7KKSfW fsmeIOFxdhBGjx8q2VcXAqKZu7ZBPX80Y2T3Ts0UQAu2To4Ew832XejAhXHZe2lg QAiBgyH571n7IpGJznXlrs6RghvaqDUm597TDvtCkMzki7Fns5w8yzxd0DO2q6lZ XbwgM8+7wlPKR/wHw3HmJJhhh9v5c4E5oMyr4obcFAdUtxti/K2T1KCESvR2mP7n VO8ebJQeRKWObuxFfbkXtl5cId9u5mpY2Cmai+shVyEYbmcXeAwlsiSurZel+BNl t2H268GPjaHdoa3jbzfRKtNDlW9ii79dH3eAi0hgv5k3rc5jxwemw== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedujedrudeijedggeeiucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpeffhffvuffkgggtuggjfgesthdtre dttdervdenucfhrhhomheptehlvhgrrhhoucfjvghrrhgvrhgruceorghlvhhhvghrrhgv segrlhhvhhdrnhhoqdhiphdrohhrgheqnecuggftrfgrthhtvghrnhepvefgleevgeeuje eghfegteeghfegheeifeehheelteetieduieeihffggfehffetnecukfhppeduledtrdel hedrudekrdejleenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfh hrohhmpegrlhhvhhgvrhhrvgesrghlvhhhrdhnohdqihhprdhorhhg X-ME-Proxy: Received: from perhan.alvh.no-ip.org (unknown [190.95.18.79]) by mail.messagingengine.com (Postfix) with ESMTPA id 7755B24005B; Thu, 3 Dec 2020 21:19:40 -0500 (EST) Received: by perhan.alvh.no-ip.org (Postfix, from userid 1000) id DF8C62A151A; Thu, 3 Dec 2020 23:19:37 -0300 (-03) Date: Thu, 3 Dec 2020 23:19:37 -0300 From: Alvaro Herrera To: Yambu Cc: Pgsql-admin Subject: Re: Moving a table/index to different tablespace Message-ID: <20201204021937.GA16616@alvherre.pgsql> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) X-Host-Lookup-Failed: Reverse DNS lookup failed for 64.147.123.20 (deferred) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On 2020-Dec-03, Yambu wrote: > Hi > > May i know if there is any risk in moving a table or index to a different > tablespace during usage? There's no risk as such, but an access exclusive lock will be acquired during the move, which will prevent all other access to that table or index.