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 <pgsql-hackers-owner+archive@lists.postgresql.org>)
	id 1iT4o7-0001qZ-GR
	for pgsql-hackers@arkaria.postgresql.org; Fri, 08 Nov 2019 14:00:11 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.89)
	(envelope-from <pgsql-hackers-owner+archive@lists.postgresql.org>)
	id 1iT4o5-0007Kp-NR
	for pgsql-hackers@arkaria.postgresql.org; Fri, 08 Nov 2019 14:00:09 +0000
Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29])
	by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256)
	(Exim 4.89)
	(envelope-from <cb@df7cb.de>)
	id 1iT4o5-0007Ki-FC
	for pgsql-hackers@lists.postgresql.org; Fri, 08 Nov 2019 14:00:09 +0000
Received: from feynman.df7cb.de ([195.49.152.168])
	by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256)
	(Exim 4.89)
	(envelope-from <cb@df7cb.de>)
	id 1iT4nz-0007ab-Nm
	for pgsql-hackers@postgresql.org; Fri, 08 Nov 2019 14:00:09 +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 478hjb2Dvpz3F19;
	Fri,  8 Nov 2019 15:00:03 +0100 (CET)
Date: Fri, 8 Nov 2019 15:00:03 +0100
From: Christoph Berg <myon@debian.org>
To: Julien Rouhaud <rjuju123@gmail.com>
Cc: PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Subject: Re: Monitoring disk space from within the server
Message-ID: <20191108140003.GK8017@msg.df7cb.de>
Mail-Followup-To: Christoph Berg <myon@debian.org>,
	Julien Rouhaud <rjuju123@gmail.com>,
	PostgreSQL Hackers <pgsql-hackers@postgresql.org>
References: <20191108132419.GG8017@msg.df7cb.de>
 <CAOBaU_YVGEnsnP1ufp42NiJ+WvPHRWBOsBOcaxWxsbXPN_sdNQ@mail.gmail.com>
 <20191108134013.GI8017@msg.df7cb.de>
 <CAOBaU_ay0FT6dFt61Pae77pHEu6sny3xM43L4i-pPi5kKkguxQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: 
 <CAOBaU_ay0FT6dFt61Pae77pHEu6sny3xM43L4i-pPi5kKkguxQ@mail.gmail.com>
User-Agent: Mutt/1.12.2 (2019-09-21)
List-Id: <pgsql-hackers.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-hackers@lists.postgresql.org>
List-Owner: <mailto:pgsql-hackers-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-hackers>
Precedence: bulk

Re: Julien Rouhaud 2019-11-08 <CAOBaU_ay0FT6dFt61Pae77pHEu6sny3xM43L4i-pPi5kKkguxQ@mail.gmail.com>
> > We could append the quotactl(Q_GETQUOTA) information as well, but I'm
> > not sure this has a sensible actual-users-to-noise ratio.
> 
> Well, having a quota is one of the few real reason to create a
> tablespace so it's probably worth it, although  I have to agree that I
> seldom saw quota in production.

Given that PG deals badly with one tablespace being full (might work
in production, but if it's full during recovery, the whole server will
stop), I've never seen quotas being used.

Christoph