Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qyJlU-007axj-2O for pgsql-docs@arkaria.postgresql.org; Wed, 01 Nov 2023 22:32:44 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1qyJlS-009KOo-LK for pgsql-docs@arkaria.postgresql.org; Wed, 01 Nov 2023 22:32:42 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qyJlS-009KOe-De for pgsql-docs@lists.postgresql.org; Wed, 01 Nov 2023 22:32:42 +0000 Received: from sss.pgh.pa.us ([68.162.161.243]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qyJlQ-004EC4-00 for pgsql-docs@lists.postgresql.org; Wed, 01 Nov 2023 22:32:41 +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 3A1MWbOk2878752; Wed, 1 Nov 2023 18:32:37 -0400 From: Tom Lane To: "David G. Johnston" cc: Bruce Momjian , "zhoushulin1992@gmail.com" , "pgsql-docs@lists.postgresql.org" Subject: Re: 'pg_global' cannot be used as default_tablespace. In-reply-to: References: <160499688847.25495.8682880307938679648@wrigleys.postgresql.org> Comments: In-reply-to "David G. Johnston" message dated "Wed, 01 Nov 2023 15:26:49 -0700" MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-ID: <2878750.1698877957.1@sss.pgh.pa.us> Content-Transfer-Encoding: 8bit Date: Wed, 01 Nov 2023 18:32:37 -0400 Message-ID: <2878751.1698877957@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk "David G. Johnston" writes: > On Wednesday, November 1, 2023, Bruce Momjian wrote: >> Did you want an error from the SET command? > That would probably be a decent addition but the request was for us to add > “it is not permissible to specify the pg_global tablespace for either > default_tablespace or temp_tablespace”. In the tablespace section per the > request but maybe also within the settings definition section. But it *is* permissible, unless we add code to reject it during SET as Bruce mentioned. Which seems fairly pointless to me. It's not like there is anything unclear about the CREATE TABLE error message. regards, tom lane