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 1pCxxW-00040y-LR for pgsql-docs@arkaria.postgresql.org; Wed, 04 Jan 2023 07:13:10 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pCxxV-0002a6-Km for pgsql-docs@arkaria.postgresql.org; Wed, 04 Jan 2023 07:13:09 +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 1pCxxV-0002Zw-Cz for pgsql-docs@lists.postgresql.org; Wed, 04 Jan 2023 07:13:09 +0000 Received: from new4-smtp.messagingengine.com ([66.111.4.230]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pCxxO-0004mD-Ic for pgsql-docs@lists.postgresql.org; Wed, 04 Jan 2023 07:13:08 +0000 Received: from compute6.internal (compute6.nyi.internal [10.202.2.47]) by mailnew.nyi.internal (Postfix) with ESMTP id 6954D5809F1; Wed, 4 Jan 2023 02:13:01 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute6.internal (MEProxy); Wed, 04 Jan 2023 02:13:01 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:date:feedback-id:feedback-id:from:from:in-reply-to :in-reply-to:message-id:mime-version:references:reply-to:sender :subject:subject:to:to:x-me-proxy:x-me-proxy:x-me-sender :x-me-sender:x-sasl-enc; s=fm2; t=1672816381; x=1672823581; bh=G MRxTdfAuuNIdnD3jDqKpXZgxRLcf4dO5OS6WsBzOvE=; b=P9WrauPHhFx7xXftg k9F57reYd7Xl/l06zkHUZxE6kH72dnad7O8wWFyIIdD0sLobm4aosSPhb69l/FTe kmGKiIk5S7DJYHSAI8CURERlBrvfl3Aqc4xPfKCc1wIbO4BUcj7amoE6cdtQkniS ke/b1kPAxKdFioQQGBk7yEio5WoSZcu9a4MnJmKQBigeWqxrYN8fBkTuArSjm/IG YCMhB6K+/BLsMHV1/JuiQjmcd13VuGZiI473zwkw40sMVTcfYDtlxe9MMH8Gphg1 8zHAzPI0CwYt/NQLgrKj7WGlVTHysb0O+vs8vjR4CZ/RkCQn2Bidyjk1mDiOq26n hvwBQ== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedrjeehgddutdejucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefkffggfgfuvfhfhfgjtgfgsehtje ertddtfeejnecuhfhrohhmpefrvghtvghrucfgihhsvghnthhrrghuthcuoehpvghtvghr rdgvihhsvghnthhrrghuthesvghnthgvrhhprhhishgvuggsrdgtohhmqeenucggtffrrg htthgvrhhnpeefjeegheetuefhveevudelueeftdejteeiffetvdduhfdtieefgfeutedt veeggfenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpe hpvghtvghrrdgvihhsvghnthhrrghuthesvghnthgvrhhprhhishgvuggsrdgtohhm X-ME-Proxy: Feedback-ID: i131946ab:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Wed, 4 Jan 2023 02:13:00 -0500 (EST) Message-ID: Date: Wed, 4 Jan 2023 08:12:58 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:102.0) Gecko/20100101 Thunderbird/102.6.0 Subject: Re: Tablespace with multiple locations Content-Language: en-US To: husseinyouness@outlook.com, pgsql-docs@lists.postgresql.org References: <167232418328.662.17750571899907598693@wrigleys.postgresql.org> From: Peter Eisentraut In-Reply-To: <167232418328.662.17750571899907598693@wrigleys.postgresql.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 29.12.22 15:29, PG Doc comments form wrote: > I m kindly requesting a clarification regarding a debatable subject in one > of my projects, that if it's possible to create one global tablespace and > assign many locations like the following example: > > create tablespace TBS1 location ('/pgdata1','/pgdata2'); What kind of clarification are you looking for? This feature doesn't exist and is not planned AFAICT.