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
https://wiki.postgresql.org/wiki/Monitoring
Thanks for the URL. I am not too keen to re-invent the wheel. Although
it teaches me on PostgreSQL.
You could also create a PostgreSQL foreign server for each of the other
databases, which would let you issue a query to UNION together the results of a
query on all of the catalogs. This would require creating a foreign table for
pg_class in the other databases.
Thanks. So many
On Fri, Mar 15, 2024 at 6:43 AM Thiemo Kellner
wrote:
> I am not sure, we are taking about the same problem, but would be
> surprised to be the only one having experienced filling disks.
...
> So, if I have a disk getting filled up, I would like to get easily
> information on the problematic
>
> On Mar 15, 2024, at 03:30, Thiemo Kellner wrote:
> Thanks for the ideas. As I would want to keep it in the database, dblink
> would be the way to go. Maybe, I will create a prodedure that creates a view
> in the monitor schema accessing the respective databases with union all to
>
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
Am 14.03.2024 um 21:03 schrieb David Rowley:
Yeah, maybe dblink and a LATERAL join might be an easy way. Something like:
create extension dblink;
select d.datname,c.relname from pg_database d, lateral (select * from
dblink('dbname='||d.datname,$$select relname from pg_class where
relname =
On Fri, 15 Mar 2024 at 07:13, David G. Johnston
wrote:
> On Thu, Mar 14, 2024, 11:08 Thiemo Kellner
> wrote:
>>
>> Thanks for the enlightenment. A pity. I suppose, there is no working
>> around this?
>
> Write a script to do the query in a loop on all databases - that catalog is
> global.
On Thu, Mar 14, 2024, 11:08 Thiemo Kellner
wrote:
> Thanks for the enlightenment. A pity. I suppose, there is no working
> around this?
Write a script to do the query in a loop on all databases - that catalog is
global.
David J.
Thanks for the enlightenment. A pity. I suppose, there is no working
around this?
Am 14.03.2024 um 18:01 schrieb Adrian Klaver:
On 3/14/24 09:41, Thiemo Kellner wrote:
Hi
I am trying to access PostgreSQL meta data, possibly in a vane attempt
to get size data.
I use DbVis with a connection
On 3/14/24 09:41, Thiemo Kellner wrote:
Hi
I am trying to access PostgreSQL meta data, possibly in a vane attempt
to get size data.
I use DbVis with a connection as shown in https://ibb.co/2SDzhXt . I try
to get information on a regular table "umsaetze". When doing the DbVis
object I can
Hi
I am trying to access PostgreSQL meta data, possibly in a vane attempt
to get size data.
I use DbVis with a connection as shown in https://ibb.co/2SDzhXt . I try
to get information on a regular table "umsaetze". When doing the DbVis
object I can see them - https://ibb.co/WxMnY2c . If I
12 matches
Mail list logo
