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/
In response to
pgsql-hackers by date
|Next:||From: Simon Riggs||Date: 2006-10-23 17:44:53|
|Subject: Re: New CRC algorithm: Slicing by 8|
|Previous:||From: Jim C. Nasby||Date: 2006-10-23 16:44:30|
|Subject: Re: PgSQL users quota|