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 1msSHu-0003ng-KE for pgsql-admin@arkaria.postgresql.org; Wed, 01 Dec 2021 16:16:54 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1msSHs-0006gy-Df for pgsql-admin@arkaria.postgresql.org; Wed, 01 Dec 2021 16:16:52 +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 1msSHs-0006gp-3H for pgsql-admin@lists.postgresql.org; Wed, 01 Dec 2021 16:16:52 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1msSHq-0000Fx-0p for pgsql-admin@lists.postgresql.org; Wed, 01 Dec 2021 16:16:51 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 1B1GGjLR1734713; Wed, 1 Dec 2021 11:16:45 -0500 From: Tom Lane To: Holger Jakobs cc: pgsql-admin@lists.postgresql.org Subject: Re: Suggestion: Explain how to move objects to the default tablespace in sql-altertable.html In-reply-to: <49d925d5-b13a-5952-0be3-fc20b271f22c@jakobs.com> References: <4011114d-e297-bb2e-ab37-9d1b3880b739@jakobs.com> <0bd53117207a26a5b8dbe03545448e72397c219f.camel@cybertec.at> <49d925d5-b13a-5952-0be3-fc20b271f22c@jakobs.com> Comments: In-reply-to Holger Jakobs message dated "Wed, 01 Dec 2021 16:49:44 +0100" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <1734711.1638375405.1@sss.pgh.pa.us> Date: Wed, 01 Dec 2021 11:16:45 -0500 Message-ID: <1734712.1638375405@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Holger Jakobs writes: > Since the default tablespace doesn't have to be mentioned in CREATing an > object, the information wouldn't be helpful there. > But when ALTERing an object in order to move it to the default > tablespace, its name has to be mentioned explicitly. That's where it's > lacking. It seems like the core misunderstanding here is closely associated with the notion that the default tablespace is "unnamed". Every tablespace has a name. I'm not sure where we might need to clarify that, but I suspect it's somewhere around the default_tablespace setting, not ALTER TABLE. regards, tom lane