| From: | Jeff Davis <pgsql(at)j-davis(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "Sergey E(dot) Koposov" <math(at)sai(dot)msu(dot)ru>, "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, pgsql-hackers(at)postgresql(dot)org, Oleg Bartunov <oleg(at)sai(dot)msu(dot)su> |
| Subject: | Re: SOC & user quotas |
| Date: | 2007-03-01 21:21:34 |
| Message-ID: | 1172784094.13722.101.camel@dogma.v10.wvs |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, 2007-02-28 at 12:56 -0500, Tom Lane wrote:
> "Sergey E. Koposov" <math(at)sai(dot)msu(dot)ru> writes:
> > Per user AND per database (as Tom noted). But I dont see what's odd in
> > it... It exists in Oracle, and I need quotas in the project on which I'm
> > working. And I remember user requests for quotas in the mailing lists ...
>
> It hasn't ever made it onto the TODO list, which means there's not a
> consensus that we need it. If it were a simple, small, low-impact patch
> then you probably wouldn't need to do much convincing that it's an
> important feature to have, but I'm afraid the patch will be none of
> those things.
>
If we allowed an admin to revoke CREATE from the pg_default tablespace,
then anyone who needed that feature could limit people to their own
tablespace (at which point it's the filesystem's job to limit their
usage). Is there some reason that we can't do this now?
Regards,
Jeff Davis
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2007-03-01 21:45:34 | Re: SOC & user quotas |
| Previous Message | Tom Lane | 2007-03-01 21:00:53 | Re: Possible Bug: high CPU usage for stats collector in 8.2 |