pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tomas Vondra <tomas.vondra@2ndquadrant.com>
To: Christoph Berg <myon@debian.org>
To: PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Subject: Re: Monitoring disk space from within the server
Date: Fri, 8 Nov 2019 15:50:25 +0100
Message-ID: <20191108145025.d7pfcip6plufxiah@development> (raw)
In-Reply-To: <20191108132419.GG8017@msg.df7cb.de>
References: <20191108132419.GG8017@msg.df7cb.de>

On Fri, Nov 08, 2019 at 02:24:19PM +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.
>

While I agree monitoring disk space is important, I think pretty much
every deployment already does that using some other monitoring tool
(which also monitors million other things).

Also, I wonder how universal / reliable this actually is, considering
the range of filesystems and related stuff (thin provisioning, quotas,
...) people use in production. I do recall a number of cases when "df"
was showing a plenty of free space, but one of the internal resources
for that particular filesystem was exhausted. I doubt it's desirable to
add all this knowledge into PostgreSQL.

It's not clear to me what issue this is actually meant to solve - it
provides data, which is nice, but it still needs to be fed to some
motinoring and alerting system. And every monitoring system has a good
plugin to collect this type of data, so why not to use that?

Surely, we can't rely on this for any internal logic - so why not to
provide this as an extension?


regards

-- 
Tomas Vondra                  http://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services





view thread (22+ messages)  latest in thread

Message-ID: <20191108145025.d7pfcip6plufxiah@development>
Permalink:  ../20191108145025.d7pfcip6plufxiah@development/
Also on:    postgresql.org/message-id/20191108145025.d7pfcip6plufxiah@development

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-hackers@postgresql.org
  Cc: tomas.vondra@2ndquadrant.com, myon@debian.org
  Subject: Re: Monitoring disk space from within the server
  In-Reply-To: <20191108145025.d7pfcip6plufxiah@development>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox