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

From Laurenz Albe
Subject Re: Monitoring disk space from within the server
Date
Msg-id 9d7165a201fe3ce3a00755b4474bb618b3ddba5e.camel@cybertec.at
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  (Michael Paquier <michael@paquier.xyz>)
List pgsql-hackers
On Fri, 2019-11-08 at 14:24 +0100, Christoph Berg 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

Will this work on Windows?
A quick web search seems to indicate that Windows has no statfs(2).

What's more is that the Linux man page says that statfs(2) is
Linux-specific.

I think that if we have such a feature (which I think would be useful)
should be available for all operating systems supported by PostgreSQL.

Yours,
Laurenz Albe




pgsql-hackers by date:

Previous
From: Laurenz Albe
Date:
Subject: Re: Option to dump foreign data in pg_dump
Next
From: Paul A Jungwirth
Date:
Subject: Re: SQL:2011 PERIODS vs Postgres Ranges?