| From: | "Jonah H(dot) Harris" <jonah(dot)harris(at)gmail(dot)com> |
|---|---|
| To: | "Jim C(dot) Nasby" <jim(at)nasby(dot)net> |
| Cc: | "Tux P" <gentuu(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: PgSQL users quota |
| Date: | 2006-10-23 17:29:49 |
| Message-ID: | 36e682920610231029o5cea639dw2fba901206c59d87@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2006-10-23 17:44:53 | Re: New CRC algorithm: Slicing by 8 |
| Previous Message | Jim C. Nasby | 2006-10-23 16:44:30 | Re: PgSQL users quota |