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 1tOgCX-0080Pv-5T for pgsql-general@arkaria.postgresql.org; Fri, 20 Dec 2024 16:50:09 +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 1tOgCW-00DsPH-0P for pgsql-general@arkaria.postgresql.org; Fri, 20 Dec 2024 16:50:07 +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 1tOgCV-00DsP9-LN for pgsql-general@lists.postgresql.org; Fri, 20 Dec 2024 16:50:07 +0000 Received: from fout-a6-smtp.messagingengine.com ([103.168.172.149]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tOgCS-000mc4-6S for pgsql-general@postgresql.org; Fri, 20 Dec 2024 16:50:06 +0000 Received: from phl-compute-12.internal (phl-compute-12.phl.internal [10.202.2.52]) by mailfout.phl.internal (Postfix) with ESMTP id 87229138020A; Fri, 20 Dec 2024 11:50:03 -0500 (EST) Received: from phl-mailfrontend-01 ([10.202.2.162]) by phl-compute-12.internal (MEProxy); Fri, 20 Dec 2024 11:50:03 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aklaver.com; h= cc:content-transfer-encoding:content-type:content-type:date:date :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:subject:subject:to:to; s=fm3; t=1734713403; x=1734799803; bh=OhDO4ok9uFHC54XfShLfj5Zvkfm2XMQMgAsN/Ce8E38=; b= lhNWQHpPMe6HLEth9RxVk0OFIKVI+fzB/Y7sGd8dYWyrUTD1VHA5kcQviuKlJPxL ZCAlH8mEUS23H8XgHE0S4DFN/kl78+8iRzxbATzd/85zxYxwvwQKOZkgSmP2wkJL Il9Z4/4Z5DkBieBV+9mK7i0upKdmY8IPCqI5M9ya7LYgDhLblqToTJ4AUHIQkCF7 QBFDLGxexLIJG660FaCT48q2YYLsuZBzy8B2dCAGBUsaGpOdTuKe+61Jck6UkZ85 Xz0goZCppw5XnzvP8cqjzOdYzH7Znv1yVQTWtexUIyH6rv6OReQuXjRnhYwW4T4L 3+tr+GSPycSs7WE7SyAhnw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :content-type:date:date:feedback-id:feedback-id:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:subject:subject:to:to:x-me-proxy:x-me-sender :x-me-sender:x-sasl-enc; s=fm1; t=1734713403; x=1734799803; bh=O hDO4ok9uFHC54XfShLfj5Zvkfm2XMQMgAsN/Ce8E38=; b=nLeedpVH2u68dLfWG uZscxP0x17EDA+H/85ReJ/A49w8Rsy6V4LPtFJ5SJl3VEfzybkp0pQUpgvxLD8K3 +2XcbGIPJ5gAJuxc95ZRlOXbfzqyATk8fK+jFN2rDLTmuyuFKuESF0cH1FJPmiqF Y8SfO0LOAougJKSVEMeLs+uJNDrdMMcFX9KbVPnLq/57ybgIOq75t8DeX1uSeWg0 0V2i2PlZJB79o+/YZatWOm1OWK4pRKo2oEuM7YQuwkaE+xm82lOLEfEWJ7pCvsPy OrT3XRHBMl5OWNutvXVseShJ3BgKc9Mk0q3CC6AVIxjM+C7kbHfksDsy3i+JFveh bBYyA== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeefuddruddtvddgleduucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdggtfgfnhhsuhgsshgtrhhisggvpdfu rfetoffkrfgpnffqhgenuceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnh htshculddquddttddmnecujfgurhepkfffgggfuffvfhfhjggtgfesthekredttddvjeen ucfhrhhomheptegurhhirghnucfmlhgrvhgvrhcuoegrughrihgrnhdrkhhlrghvvghrse grkhhlrghvvghrrdgtohhmqeenucggtffrrghtthgvrhhnpeelgeevkeekkeeuiefgtdev ieeluefhfedufeetkeejffekjeeujeehgeehgeektdenucffohhmrghinhepphhoshhtgh hrvghsqhhlrdhorhhgnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghi lhhfrhhomheprggurhhirghnrdhklhgrvhgvrhesrghklhgrvhgvrhdrtghomhdpnhgspg hrtghpthhtohepvddpmhhouggvpehsmhhtphhouhhtpdhrtghpthhtohepvghsthgvvghm sghsvhdqfhhorhhumheshigrhhhoohdrtghomhdprhgtphhtthhopehpghhsqhhlqdhgvg hnvghrrghlsehpohhsthhgrhgvshhqlhdrohhrgh X-ME-Proxy: Feedback-ID: i76984098:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Fri, 20 Dec 2024 11:50:02 -0500 (EST) Message-ID: Date: Fri, 20 Dec 2024 08:50:01 -0800 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: cannot drop a tablespace which never exists in pg_tablespace To: Bharani SV-forum , pgsql-general References: <0558ddd4d71641bdb41fa49b2425f73c@safrangroup.com> <07ab2d83-ffe5-4bec-9626-22a68f732579@aklaver.com> <273a88dc-4134-47d5-bc19-30ff5f97926c@aklaver.com> <498dfb34-4dd7-4f48-8188-355e1488d7e6@aklaver.com> <1061066336.5835157.1733316137292@mail.yahoo.com> <1918413683.2239751.1733944364448@mail.yahoo.com> <037a8338-3434-47d4-aaad-ef186d4d3250@aklaver.com> <101139100.4053671.1734383960480@mail.yahoo.com> <1875422740.4095620.1734388259706@mail.yahoo.com> <1528119631.4096246.1734390318281@mail.yahoo.com> <2033286177.1733661.1734651404850@mail.yahoo.com> <8833d8c7-3713-4d6f-9eab-35270e769564@aklaver.com> <1392047062.5689697.1734710997053@mail.yahoo.com> Content-Language: en-US From: Adrian Klaver In-Reply-To: <1392047062.5689697.1734710997053@mail.yahoo.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 12/20/24 08:09, Bharani SV-forum wrote: > Adrian > Inline image > > initially i had created tblspace outside pg_data env variable Did you run CREATE TABLESPACE as shown below?: https://www.postgresql.org/docs/current/sql-createtablespace.html Did you ever use the tablespace? > e.g PG_DATA env variable is defined to /XXX/YYYY/ABC/15/data > > the tablespace was created under  /XXX/YYYY/ABC/15/tblspace/<>/ > assume tablespace name is abc_data > > *cd /XXX/YYYY/ABC/15/tblspace/abc_data/* > ls -atl > drwxr-x---. 2 postgres postgres  6 Dec 19 22:08 PG_15_202209061 > > ls -altR > drwxr-x---. 2 postgres postgres  6 Dec 19 22:08 PG_15_202209061 > > i reconfirmed > SELECT * FROM pg_tablespace ; >  oid  |  spcname   | spcowner | spcacl | spcoptions > ------+------------+----------+--------+------------ >  1663 | pg_default |       10 |        | >  1664 | pg_global  |       10 |        | > > not having any entry about tablespace abc_data > > Can you guide > -- Adrian Klaver adrian.klaver@aklaver.com