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 1sY6TQ-008qZC-7D for pgsql-admin@arkaria.postgresql.org; Sun, 28 Jul 2024 16:10:16 +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 1sY6TO-00C5HE-P4 for pgsql-admin@arkaria.postgresql.org; Sun, 28 Jul 2024 16:10:14 +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 1sY6TO-00C5H5-DN for pgsql-admin@lists.postgresql.org; Sun, 28 Jul 2024 16:10:14 +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 1sY6TM-001vMz-9b for pgsql-admin@lists.postgresql.org; Sun, 28 Jul 2024 16:10:13 +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 46SGAAFU2253444; Sun, 28 Jul 2024 12:10:10 -0400 From: Tom Lane To: "David G. Johnston" cc: Stepan Neretin , "pgsql-admin@lists.postgresql.org" Subject: Re: SubTablespaces(Recursive) expected behaviour? In-reply-to: References: Comments: In-reply-to "David G. Johnston" message dated "Sun, 28 Jul 2024 09:05:14 -0700" MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-ID: <2253442.1722183010.1@sss.pgh.pa.us> Content-Transfer-Encoding: 8bit Date: Sun, 28 Jul 2024 12:10:10 -0400 Message-ID: <2253443.1722183010@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 Sunday, July 28, 2024, Stepan Neretin wrote: >> Hi, David. I have read this page several times and have not answered my >> question. I'm probably not paying attention. Can you, I wanted to quote >> what I'm missing out on > “The location must be an existing, empty directory that is owned by the > PostgreSQL operating system user.” Indeed, that doesn't directly answer the question, but I think the implication is clear: we do not expect a tablespace directory to contain anything except files that Postgres itself puts there. I don't actually see the point of the described setup anyway. There is zero value that I can see in putting two tablespaces on the same physical volume --- they won't provide any interesting separation. regards, tom lane