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 1gMemE-0005k6-S3 for pgsql-hackers@arkaria.postgresql.org; Tue, 13 Nov 2018 19:55:11 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1gMemC-0003xp-M2 for pgsql-hackers@arkaria.postgresql.org; Tue, 13 Nov 2018 19:55:08 +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 1gMelo-000210-4i for pgsql-hackers@lists.postgresql.org; Tue, 13 Nov 2018 19:54:44 +0000 Received: from mail-wm1-x344.google.com ([2a00:1450:4864:20::344]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gMelk-0004wh-1C for pgsql-hackers@postgresql.org; Tue, 13 Nov 2018 19:54:42 +0000 Received: by mail-wm1-x344.google.com with SMTP id f19-v6so11954251wmb.0 for ; Tue, 13 Nov 2018 11:54:39 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=2ndquadrant-com.20150623.gappssmtp.com; s=20150623; h=message-id:subject:from:to:date:in-reply-to:references:mime-version :content-transfer-encoding; bh=5jYWHji0zt8N+NJnoqwYkurhPIlzOTSunBBapz9PbpM=; b=bBV4JvUWsVGLHWJl+dyn92XpgMjtKwpmZHthAZH7ccY/jwxP00KagcUU1cTUiBmOh2 uVJqbIt5mqBrLnMU3E0Pf49DcUOelyS3JvXm+p29JyF7ezgl3cfbpaZrWDddq9G5m2fb SFr0fKlGgQT0laLz1oPs6W/u2+h7IPCPWQT5AFT/3UOcQboi53+jA/5LfXaV2ILtGY1S ucVTkiEIfQef7MlScVu0Ac35dXMXj2GOMgcWjuI/+EUW1M0JmxbUx89OGANh/bpb7Jy2 RgMObmwB108aGc8HTTTH7AK/ijlvaspdEwPOA9zFfcxdtzToF3Nl1Fa1uItIQZWtkVjx g+Vw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:message-id:subject:from:to:date:in-reply-to :references:mime-version:content-transfer-encoding; bh=5jYWHji0zt8N+NJnoqwYkurhPIlzOTSunBBapz9PbpM=; b=Zd9D9jr/j8ZFhaPG92BOkGsmXa6fIwEY+sRrfF/ihxPgSDS0t3VTmmjSh99WixJX7d K44/zxILAZp4DFluPlVFrEkMUTH/uuu638GXNAm4hz6e7fVX8s+gZI14cdTeZiBCWG2V f9WB61takw9mhBoEpxOltbygx5dx8IlYPWxMCMTR9RLGg2BA7FFKR0MhrXoar2ufT1Kd uO6ZvbbFyOnT0PgzVl5gQZjxL/7vs/doCgSMwdLxnd1neGlCqE6QiSeNf2QgdRX1p0mX cNtS/9O0DMP3+JcYL61cjYuclPup22Dy4oQOYYkYwjX1xsRexde/dZicNmkrWVucfXY8 JPtQ== X-Gm-Message-State: AGRZ1gLJaRy5vQH5gxjd+q2uHJybYmT+RncXV3Z+a5pVkfflTVlHOs1u 6FvVUwd82UVAg3UjFGRMMotJ3qyjkHU= X-Google-Smtp-Source: AJdET5eg4d68ynCP1ItJI2qdm7vyGLH5Hmg//ZztEtEGSmbJi5dcU44X1UEDxmx4e2Xe6OxyssOtSQ== X-Received: by 2002:a1c:cb01:: with SMTP id b1-v6mr4379854wmg.124.1542138877401; Tue, 13 Nov 2018 11:54:37 -0800 (PST) Received: from development (static-84-42-175-93.net.upcbroadband.cz. [84.42.175.93]) by smtp.gmail.com with ESMTPSA id u14-v6sm24005708wrs.27.2018.11.13.11.54.36 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Tue, 13 Nov 2018 11:54:36 -0800 (PST) Message-ID: Subject: Re: Control your disk usage in PG: Introduction to Disk Quota Extension From: Tomas Vondra To: Hubert Zhang , PostgreSQL Hackers Date: Tue, 13 Nov 2018 20:54:34 +0100 In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.28.5 (3.28.5-2.fc28) Mime-Version: 1.0 Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On Tue, 2018-11-13 at 16:47 +0800, Hubert Zhang wrote: > Hi all, > > We implement disk quota feature on Postgresql as an extension(link: > https://github.com/greenplum-db/diskquota), > If you are interested, try and use it to limit the amount of disk > space that > a schema or a role can use in Postgresql. > Any feedback or question are appreciated. > It's not clear to me what's the goal of this thread? I understand what quotas are about, but are you sharing it because (a) it's a useful extension, (b) you propose adding a couple of new hooks (and keep the extension separate) or (c) you propose adding both the hooks and the extension (into contrib)? I assume it's either (b) and (c), in which case you should add it to 2019-01 CF: https://commitfest.postgresql.org/21/ In either case, it might be useful to add a LICENSE to the github repository, it's not clear what's the situation in this respect. That probably matters especially for (b), because for (c) it'd end up with PostgreSQL license automatically. regards -- Tomas Vondra http://www.2ndQuadrant.com PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services