Re: PgSQL users quota - Mailing list pgsql-hackers

From Jonah H. Harris
Subject Re: PgSQL users quota
Date
Msg-id 36e682920610231029o5cea639dw2fba901206c59d87@mail.gmail.com
Whole thread Raw
In response to Re: PgSQL users quota  ("Jim C. Nasby" <jim@nasby.net>)
Responses Re: PgSQL users quota  ("Tux P" <gentuu@gmail.com>)
List pgsql-hackers
On 10/23/06, Jim C. Nasby <jim@nasby.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@enterprisedb.com
Iselin, New Jersey 08830            | http://www.enterprisedb.com/


pgsql-hackers by date:

Previous
From: "Jim C. Nasby"
Date:
Subject: Re: PgSQL users quota
Next
From: "Simon Riggs"
Date:
Subject: Re: New CRC algorithm: Slicing by 8