Re: Monitoring disk space from within the server

From: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
To: Christoph Berg <myon(at)debian(dot)org>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Monitoring disk space from within the server
Date: 2019-11-11 20:11:35
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: 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

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.

Laurenz Albe

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Paul A Jungwirth 2019-11-11 20:13:20 Re: SQL:2011 PERIODS vs Postgres Ranges?
Previous Message Laurenz Albe 2019-11-11 20:04:17 Re: Option to dump foreign data in pg_dump