From: Adrian Klaver <adrian.klaver@aklaver.com>
To: Thiemo Kellner <thiemo@gelassene-pferde.biz>
To: pgsql-general@lists.postgresql.org <pgsql-general@lists.postgresql.org>
Subject: Re: select results on pg_class incomplete
Date: Fri, 15 Mar 2024 08:14:06 -0700
Message-ID: <df4a979f-2f92-4012-bddb-ceb23f3ed853@aklaver.com> (raw)
In-Reply-To: <f78d498c-e800-4b6d-b72d-ae38011b51c8@gelassene-pferde.biz>
References: <7a8e0759-1ba7-47e4-a6f8-8aa4095ec31c@gelassene-pferde.biz>
<926324EB-5E21-49CC-9C1B-3CDA2FD9A6F0@2bz.de>
<f78d498c-e800-4b6d-b72d-ae38011b51c8@gelassene-pferde.biz>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-general@postgresql.org
Cc: adrian.klaver@aklaver.com, thiemo@gelassene-pferde.biz
Subject: Re: select results on pg_class incomplete
In-Reply-To: <df4a979f-2f92-4012-bddb-ceb23f3ed853@aklaver.com>
References: <7a8e0759-1ba7-47e4-a6f8-8aa4095ec31c@gelassene-pferde.biz> <926324EB-5E21-49CC-9C1B-3CDA2FD9A6F0@2bz.de> <f78d498c-e800-4b6d-b72d-ae38011b51c8@gelassene-pferde.biz> <df4a979f-2f92-4012-bddb-ceb23f3ed853@aklaver.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox