Re: PgSQL users quota

Hi .*

Is there any chance to see the quota implementation described in this post
in any next releases?

http://archives.postgresql.org/pgsql-hackers/2004-07/msg00392.php

Thanks you!
----
Nick

On Fri, Oct 20, 2006 at 03:30:40AM +0300, Tux P wrote:
> Hi .*
>
> Is there any chance to see the quota implementation described in this post
> in any next releases?
>
> http://archives.postgresql.org/pgsql-hackers/2004-07/msg00392.php

Since Jonah hasn't done anything with it he's presumably lost interest,
so you'd need to find someone else looking for an itch to scratch. And
it appears the original patch was against 7.4, so it'd probably need a
decent amount of work to make it work with our current code.

On the bright side, there is the following TODO item:

o Allow per-tablespace quotas
--
Jim Nasby jim(at)nasby(dot)net
EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)

On 10/23/06, Jim C. Nasby <jim(at)nasby(dot)net> wrote:
> Since Jonah hasn't done anything with it he's presumably lost interest,
> so you'd need to find someone else looking for an itch to scratch. And
> it appears the original patch was against 7.4, so it'd probably need a
> decent amount of work to make it work with our current code.

Well, it was more of the case of community wants vs. what I needed at
the time. I'm not quite sure if I have the patch lying around
anywhere, but it was fairly trivial to implement.

> o Allow per-tablespace quotas

Yes, this is what came out of the discussion. A per-tablespace patch
should be fairly easy to implement once you get a consensus on what
constitutes actual space usage... as VACUUMable space may or may not
apply depending on your use-case.

--
Jonah H. Harris, Software Architect | phone: 732.331.1300
EnterpriseDB Corporation | fax: 732.331.1301
33 Wood Ave S, 2nd Floor | jharris(at)enterprisedb(dot)com
Iselin, New Jersey 08830 | http://www.enterprisedb.com/

Thanks for your response.

Waiting on anyone to implement this feature ;))
-----
Nick

2006/10/23, Jonah H. Harris <jonah(dot)harris(at)gmail(dot)com>:
>
> On 10/23/06, Jim C. Nasby <jim(at)nasby(dot)net> wrote:
> > Since Jonah hasn't done anything with it he's presumably lost interest,
> > so you'd need to find someone else looking for an itch to scratch. And
> > it appears the original patch was against 7.4, so it'd probably need a
> > decent amount of work to make it work with our current code.
>
> Well, it was more of the case of community wants vs. what I needed at
> the time. I'm not quite sure if I have the patch lying around
> anywhere, but it was fairly trivial to implement.
>
> > o Allow per-tablespace quotas
>
> Yes, this is what came out of the discussion. A per-tablespace patch
> should be fairly easy to implement once you get a consensus on what
> constitutes actual space usage... as VACUUMable space may or may not
> apply depending on your use-case.
>
> --
> Jonah H. Harris, Software Architect | phone: 732.331.1300
> EnterpriseDB Corporation | fax: 732.331.1301
> 33 Wood Ave S, 2nd Floor | jharris(at)enterprisedb(dot)com
> Iselin, New Jersey 08830 | http://www.enterprisedb.com/
>