From: | Greg Sabino Mullane <htamfids(at)gmail(dot)com> |
---|---|
To: | Thiemo Kellner <thiemo(at)gelassene-pferde(dot)biz> |
Cc: | "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
Subject: | Re: select results on pg_class incomplete |
Date: | 2024-03-15 13:46:21 |
Message-ID: | CAKAnmm+HenOQJTDc5kpQOa+w1-j6hG0=B3O9WtcDaPPM46+EBg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Fri, Mar 15, 2024 at 6:43 AM Thiemo Kellner <thiemo(at)gelassene-pferde(dot)biz>
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
> structures in one go.
This is a common problem, and one that has been solved before. There are
many monitoring solutions out there that can help you with this. For an
incomplete list, see:
https://wiki.postgresql.org/wiki/Monitoring
If you want to roll your own, the other thread is full of good information
on that.
Cheers,
Greg
From | Date | Subject | |
---|---|---|---|
Next Message | Thiemo Kellner | 2024-03-15 13:49:02 | Re: select results on pg_class incomplete |
Previous Message | Greg Sabino Mullane | 2024-03-15 13:40:08 | Re: operator is only a shell - Error |