Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1iUS6F-0004MS-E6 for pgsql-hackers@arkaria.postgresql.org; Tue, 12 Nov 2019 09:04:35 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1iUS6E-0005Je-6R for pgsql-hackers@arkaria.postgresql.org; Tue, 12 Nov 2019 09:04:34 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1iUS6D-0005JX-Qv for pgsql-hackers@lists.postgresql.org; Tue, 12 Nov 2019 09:04:33 +0000 Received: from feynman.df7cb.de ([195.49.152.168]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1iUS67-0002c4-CT for pgsql-hackers@postgresql.org; Tue, 12 Nov 2019 09:04:32 +0000 Received: from msg.df7cb.de (unknown [IPv6:2003:5b:203b:100:7627:eaff:fe52:8e03]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by feynman.df7cb.de (Postfix) with ESMTPSA id 47C1yc4SRlz3F13; Tue, 12 Nov 2019 10:04:24 +0100 (CET) Date: Tue, 12 Nov 2019 10:04:24 +0100 From: Christoph Berg To: Daniel Gustafsson Cc: Michael Paquier , Christoph Moench-Tegeder , Julien Rouhaud , PostgreSQL Hackers Subject: Re: Monitoring disk space from within the server Message-ID: <20191112090424.GA20731@msg.df7cb.de> Mail-Followup-To: Christoph Berg , Daniel Gustafsson , Michael Paquier , Christoph Moench-Tegeder , Julien Rouhaud , PostgreSQL Hackers References: <20191108132419.GG8017@msg.df7cb.de> <20191108133531.GH8017@msg.df7cb.de> <20191108135830.GJ8017@msg.df7cb.de> <20191109015618.GB5128@paquier.xyz> <20191109133349.GA2545@elch.exwg.net> <20191112014641.GC1549@paquier.xyz> <7A3B9BB6-BEA0-466E-98A9-B4DD8F04830E@yesql.se> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <7A3B9BB6-BEA0-466E-98A9-B4DD8F04830E@yesql.se> User-Agent: Mutt/1.12.2 (2019-09-21) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Re: Daniel Gustafsson 2019-11-12 <7A3B9BB6-BEA0-466E-98A9-B4DD8F04830E@yesql.se> > I agree with Tomas upthread that it's unclear whether this needs to be in core. > There are many system parameters a database admin is likely to be interested > in, diskspace being just one of them (albeit a very important one for many > reasons), and there is nothing that makes the SQL interface (or postgres core > for that matter) particularly more suited for this job than other existing > tools. > > Why is SQL level crucial for this? Because the figure is interesting to users as well. They will usually not have any access to monitoring, and checking if they can load this extra 10 GB dataset is a good use case. This is about providing the numbers in the place where they are needed. Of course admins can just go elsewhere to look it up (and probably will), but I think now there's a usability gap for people who just have SQL access. Christoph