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 1tOQDl-006DNG-QM for pgsql-general@arkaria.postgresql.org; Thu, 19 Dec 2024 23:46:22 +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 1tOQDk-001vN8-Hs for pgsql-general@arkaria.postgresql.org; Thu, 19 Dec 2024 23:46:20 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tOQDj-001vMz-78 for pgsql-general@lists.postgresql.org; Thu, 19 Dec 2024 23:46:19 +0000 Received: from fout-b7-smtp.messagingengine.com ([202.12.124.150]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tOQDc-000SeG-1M for pgsql-general@postgresql.org; Thu, 19 Dec 2024 23:46:17 +0000 Received: from phl-compute-03.internal (phl-compute-03.phl.internal [10.202.2.43]) by mailfout.stl.internal (Postfix) with ESMTP id 59F1A11400AF; Thu, 19 Dec 2024 18:46:10 -0500 (EST) Received: from phl-mailfrontend-02 ([10.202.2.163]) by phl-compute-03.internal (MEProxy); Thu, 19 Dec 2024 18:46:10 -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=1734651970; x=1734738370; bh=xH0BdUhciW9+nbmx8G1N8iGhyiQU8jUTXaRa8HbYJPI=; b= J+lWzsEPFhBtnQD5ToMCscqltyyOiTVzpn4HCJGpM/ybQvLfqgC+6XvSJc8F/Pwd I/yu60ChWnVeHm6XK09OogerF83zHyuHpmpPOzXUNxVujam+S7u+3d/NHqTgB0xT 26H0szgI+NC5CujQZBIytbwM6AF7GdP1UhOj//yIWdtmUFak4NII5AYDPwz2HepP OgWlXLtGC5wSL9qjyyhlMdBr/wEA5fe01iuHWGE+WBSZDBW6OL9ADDTQOZKHVsnW E8k+ixE0n3RHva68q50BUBTxF8N2OhjaBsuW97/tgfWcINY+8lZy5J/m+0TnKjMt GucQL+5GufsYPxa4xXNSCA== 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=1734651970; x=1734738370; bh=x H0BdUhciW9+nbmx8G1N8iGhyiQU8jUTXaRa8HbYJPI=; b=3bLGGeLXwPAD7oM7j kCqECWnoi2BLXx+tdqwBDia0W2VOGIzU2U/nG8MGbbuwRaVCF0fa3n7Ul3TRUthO VsIt16QXGrwmkbTY/kE+hBDARwNQ2YFPQnakZcLw2O7wc4MdjXLi+lbeO7gEfvHh 59D8ift2U+6vDjGbExvP6siJLeLa6I9iOyuIy77ZghQ8gRdbIrgUsz27mLNLdM9x yGw9/7POJcQTBhxNK34KBQEichTA35sw/K3pfYnOx2ObMAEdjJV2tHCt+gQrcDZI 3OmX+Wu744/LzbLyQYzh73vlQb2fuREdbUNVeAkFc2tX2j0eAM8+chHoIIFU/4MT jNBHA== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeefuddruddtuddgudefucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdggtfgfnhhsuhgsshgtrhhisggvpdfu rfetoffkrfgpnffqhgenuceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnh htshculddquddttddmnecujfgurhepkfffgggfuffvfhfhjggtgfesthejredttddvjeen ucfhrhhomheptegurhhirghnucfmlhgrvhgvrhcuoegrughrihgrnhdrkhhlrghvvghrse grkhhlrghvvghrrdgtohhmqeenucggtffrrghtthgvrhhnpeekfeehuddvjeeigfeifeej tdduudffledvfeelheeftdeiffeugfdvkeelgedtvdenucffohhmrghinhepphhoshhtgh hrvghsqhhlrdhorhhgnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghi lhhfrhhomheprggurhhirghnrdhklhgrvhgvrhesrghklhgrvhgvrhdrtghomhdpnhgspg hrtghpthhtohepvddpmhhouggvpehsmhhtphhouhhtpdhrtghpthhtohepvghsthgvvghm sghsvhdqfhhorhhumheshigrhhhoohdrtghomhdprhgtphhtthhopehpghhsqhhlqdhgvg hnvghrrghlsehpohhsthhgrhgvshhqlhdrohhrgh X-ME-Proxy: Feedback-ID: i76984098:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Thu, 19 Dec 2024 18:46:09 -0500 (EST) Message-ID: <8833d8c7-3713-4d6f-9eab-35270e769564@aklaver.com> Date: Thu, 19 Dec 2024 15:46:06 -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> <98965993.3138805.1731699978332@mail.yahoo.com> <564950518.5117550.1733177884387@mail.yahoo.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> Content-Language: en-US From: Adrian Klaver In-Reply-To: <2033286177.1733661.1734651404850@mail.yahoo.com> 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 12/19/24 15:36, Bharani SV-forum wrote: > > cannot drop a tablespace which never exists in pg_tablespace > > I remember i had create previously an tablespace named " mq_data" , but > cannot find in pg_tablespace listing. > > if i try to create the same tablespace name, it is giving error as " > already in use as a tablespace" > how to force drop the pointer entry and the tablespace from postgres From: https://www.postgresql.org/docs/current/manage-ag-tablespaces.html "The directory $PGDATA/pg_tblspc contains symbolic links that point to each of the non-built-in tablespaces defined in the cluster." Is there a symlink at the above location? Does the directory in the image have files? > > Inline image > -- Adrian Klaver adrian.klaver@aklaver.com