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 1rl9GC-000NnP-QF for pgsql-general@arkaria.postgresql.org; Fri, 15 Mar 2024 15:14:17 +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 1rl9GA-009u1F-Oi for pgsql-general@arkaria.postgresql.org; Fri, 15 Mar 2024 15:14:15 +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 1rl9G9-009u17-2C for pgsql-general@lists.postgresql.org; Fri, 15 Mar 2024 15:14:14 +0000 Received: from fhigh3-smtp.messagingengine.com ([103.168.172.154]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rl9G5-004f8k-1v for pgsql-general@lists.postgresql.org; Fri, 15 Mar 2024 15:14:12 +0000 Received: from compute7.internal (compute7.nyi.internal [10.202.2.48]) by mailfhigh.nyi.internal (Postfix) with ESMTP id 2C675114011A; Fri, 15 Mar 2024 11:14:08 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute7.internal (MEProxy); Fri, 15 Mar 2024 11:14:08 -0400 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=1710515648; x=1710602048; bh=TjXaKcMXXvIB7GPu7ZGafgYFL4XWCqNWfvOuMCYSO/4=; b= kjXJFcRl0UbSW/KmzPUpIIWucnxkr/BDZWXt/V+5taalB438RybrMQyw1h3H9YoQ rkwdWcTc+5J4/qN+qW2NsTNwSPnXsoKiGZfiR9P1PaT5IsGyzYtedI3U7C8coAoA bg/lbMCn4uJZNaptN9bMFhNHU4ufN3kQTEYemEu255G4TB7XIdKqREBWVTpZoYuP OjpH5o1/UDQbNWR3d6Pl4S13Sd6+pyBa74l4b5f8UxB0qmpy//gFIls3mPAaIibZ eR+5Clh/b+ofL9AOx1rD8REPC7O/0CILHLY6in3zic/VuyS/CYTapomiDLemIVAn Et+AMPpmbegLdSnCd7OQKw== 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-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm1; t=1710515648; x= 1710602048; bh=TjXaKcMXXvIB7GPu7ZGafgYFL4XWCqNWfvOuMCYSO/4=; b=l WUwiDTe1ubllELBXoyNudff8kfXIbpdvUzylfP/lN6CqosEpO7pAkhV1HEJ8mM7d Z92WSvCCQVEO25r75gxghcDzdyGRtQDPicK55S8ebIco7NkDlOFp0k/nHuswRdYT zQzVb8iWZjUHuSxgva9RdGWv6gITSGIgwbcoCmd0sI2Nce/c2c513uNvr9OiIoMA Vp2V1BxJ02gJYpIVQkC20VtTuiT+r2LG6IwkQbZvsE286OrBHKLqLYIhfClpbfuX A0t1JGQNoXOvf8PkQP+dCn8UM6UzjmUI5eRX6Yu/gf5Kd05mndG3EgCzh59xLadm sV31YpM17LgDOaIljraFA== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvledrjeelgdejfecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefkffggfgfuvfhfhfgjtgfgsehtjeertddtvdejnecuhfhrohhmpeetughrihgr nhcumfhlrghvvghruceorggurhhirghnrdhklhgrvhgvrhesrghklhgrvhgvrhdrtghomh eqnecuggftrfgrthhtvghrnhepiedvhfeiheehgeeuieeljeeitedtjeehudegfeelkedv leekhedtgfeiffefkedunecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrg hilhhfrhhomheprggurhhirghnrdhklhgrvhgvrhesrghklhgrvhgvrhdrtghomh X-ME-Proxy: Feedback-ID: i76984098:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Fri, 15 Mar 2024 11:14:07 -0400 (EDT) Message-ID: Date: Fri, 15 Mar 2024 08:14:06 -0700 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: select results on pg_class incomplete To: Thiemo Kellner , "pgsql-general@lists.postgresql.org" References: <7a8e0759-1ba7-47e4-a6f8-8aa4095ec31c@gelassene-pferde.biz> <926324EB-5E21-49CC-9C1B-3CDA2FD9A6F0@2bz.de> Content-Language: en-US From: Adrian Klaver In-Reply-To: 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 3/15/24 03:42, Thiemo Kellner wrote: >> You solve a problem that no one has. Data belonging together may still >> be divided into schemas in a database. Thus, the metadata is also >> reported and archived individually per database. > > I am not sure, we are taking about the same problem, but would be > surprised to be the only one having experienced filling disks. Maybe, I > am just that old already that disk space has become so cheep, the > problem does not exist any longer. > > With respect to metadata and databases: The point is not that I cannot > see the tables in another schema (I believe, did not check yet), but in > other databases. While this actually does not matter much, I still hold That is backwards, schemas are namespaces within a database you can see their contents from the local(database) system catalogs. > it true that a disk getting filled up does not care in which database or > schema a explosively growing table resides. So, if I have a disk getting > filled up, I would like to get easily information on the problematic > structures in one go. With PostgreSQL this does not seem to be possible > out of the box. I now can query each database separately, or I can > create auxiliary structures like dblink and views to accommodate for a > "single" query solution. My two dimes. > > -- Adrian Klaver adrian.klaver@aklaver.com