MIME-Version: 1.0
References: 
 <CAB0yre=RP_ho6Bq4cV23ELKxRcfhV2Yqrb1zHp0RfUPEWCnBRw@mail.gmail.com>
 <eface0f387a6f7530862ef40e3e3e55ac915ea83.camel@2ndquadrant.com>
In-Reply-To: <eface0f387a6f7530862ef40e3e3e55ac915ea83.camel@2ndquadrant.com>
From: Hubert Zhang <hzhang@pivotal.io>
Date: Wed, 14 Nov 2018 18:06:09 +0800
Message-ID: 
 <CAB0yrenHV2iw4hQEnHGkTTpXZN8jMUJNtsCV4=BmWckjnn16Mg@mail.gmail.com>
Subject: Re: Control your disk usage in PG: Introduction to Disk Quota
 Extension
To: tomas.vondra@2ndquadrant.com
Cc: PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Content-Type: multipart/alternative; boundary="00000000000000477d057a9d1695"
Precedence: bulk


--00000000000000477d057a9d1695
Content-Type: text/plain; charset="UTF-8"

Thanks, Tomas,

Yes, we want to add the hooks into postgres repo.
But before that, we plan to firstly get some feedbacks from community about
the diskquota extension implementation and usage?
Later, we'll modify our license and submit the hooks into CF.

Thanks
Hubert

On Wed, Nov 14, 2018 at 3:54 AM Tomas Vondra <tomas.vondra@2ndquadrant.com>
wrote:

> 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
>
>

-- 
Thanks

Hubert Zhang

--00000000000000477d057a9d1695
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Thanks, Tomas,<div><br></div><div>Yes, we want to add the =
hooks into postgres repo.</div><div>But before that, we plan to firstly get=
 some feedbacks from community about the diskquota extension implementation=
 and usage?=C2=A0</div><div>Later, we&#39;ll modify our license and submit =
the hooks into CF.</div><div><br></div><div>Thanks</div><div>Hubert</div></=
div><br><div class=3D"gmail_quote"><div dir=3D"ltr">On Wed, Nov 14, 2018 at=
 3:54 AM Tomas Vondra &lt;<a href=3D"mailto:tomas.vondra@2ndquadrant.com">t=
omas.vondra@2ndquadrant.com</a>&gt; wrote:<br></div><blockquote class=3D"gm=
ail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-le=
ft:1ex">On Tue, 2018-11-13 at 16:47 +0800, Hubert Zhang wrote:<br>
&gt; Hi all,<br>
&gt; <br>
&gt; We implement disk quota feature on Postgresql as an extension(link:<br=
>
&gt; <a href=3D"https://github.com/greenplum-db/diskquota" rel=3D"noreferre=
r" target=3D"_blank">https://github.com/greenplum-db/diskquota</a>),<br>
&gt; If you are interested, try and use it to limit the amount of disk<br>
&gt; space that<br>
&gt; a schema or a role can use in Postgresql.<br>
&gt; Any feedback or question are appreciated.<br>
&gt; <br>
<br>
It&#39;s not clear to me what&#39;s the goal of this thread? I understand w=
hat<br>
quotas are about, but are you sharing it because (a) it&#39;s a useful<br>
extension, (b) you propose adding a couple of new hooks (and keep the<br>
extension separate) or (c) you propose adding both the hooks and the<br>
extension (into contrib)?<br>
<br>
I assume it&#39;s either (b) and (c), in which case you should add it to<br=
>
2019-01 CF: <a href=3D"https://commitfest.postgresql.org/21/" rel=3D"norefe=
rrer" target=3D"_blank">https://commitfest.postgresql.org/21/</a><br>
<br>
In either case, it might be useful to add a LICENSE to the github<br>
repository, it&#39;s not clear what&#39;s the situation in this respect. Th=
at<br>
probably matters especially for (b), because for (c) it&#39;d end up with<b=
r>
PostgreSQL license automatically.<br>
<br>
regards<br>
<br>
-- <br>
Tomas Vondra=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
<a href=3D"http://www.2ndQuadrant.com" rel=3D"noreferrer" target=3D"_blank"=
>http://www.2ndQuadrant.com</a><br>
PostgreSQL Development, 24x7 Support, Remote DBA, Training &amp; Services<b=
r>
<br>
</blockquote></div><br clear=3D"all"><div><br></div>-- <br><div dir=3D"ltr"=
 class=3D"gmail_signature" data-smartmail=3D"gmail_signature"><div dir=3D"l=
tr">Thanks<div><br></div><div>Hubert Zhang</div></div></div>

--00000000000000477d057a9d1695--