Re: Monitoring disk space from within the server - Mailing list pgsql-hackers

From Julien Rouhaud
Subject Re: Monitoring disk space from within the server
Date
Msg-id CAOBaU_YVGEnsnP1ufp42NiJ+WvPHRWBOsBOcaxWxsbXPN_sdNQ@mail.gmail.com
Whole thread Raw
In response to Monitoring disk space from within the server  (Christoph Berg <myon@debian.org>)
Responses Re: Monitoring disk space from within the server  (Christoph Berg <myon@debian.org>)
Re: Monitoring disk space from within the server  (Christoph Berg <myon@debian.org>)
List pgsql-hackers
On Fri, Nov 8, 2019 at 2:24 PM Christoph Berg <myon@debian.org> wrote:
>
> Monitoring the available disk space is the topmost thing on the
> priority for PostgreSQL operation, yet this metric is not available
> from the SQL level.
>
> The attached patch implements a function pg_tablespace_statfs(tblspc)
> to report disk space numbers per tablespace:
>
> # select * from pg_tablespace_statfs('pg_default');
>   blocks   │  bfree   │  bavail  │  files   │  ffree
> ───────────┼──────────┼──────────┼──────────┼──────────
>  103179564 │ 20829222 │ 20815126 │ 26214400 │ 24426295
>
> Open points:
> * should these numbers be converted to bytes?
> * the column names currently mirror the statfs() names and should
>   certainly be improved
> * which of these columns add to \db+ output?
> * possibly extend this (and \db) to pg_wal

Shouldn't we have something more generic, in hope that this eventually
get implemented on Windows?  I'm also wondering if getting the fs
information is enough, as there might be quota.



pgsql-hackers by date:

Previous
From: Konstantin Knizhnik
Date:
Subject: Re: Why overhead of SPI is so large?
Next
From: Christoph Berg
Date:
Subject: Re: Monitoring disk space from within the server