Re: SOC & user quotas - Mailing list pgsql-hackers

From Jeff Davis
Subject Re: SOC & user quotas
Date
Msg-id 1172784094.13722.101.camel@dogma.v10.wvs
Whole thread Raw
In response to Re: SOC & user quotas  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: SOC & user quotas  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: SOC & user quotas  (Andrew Dunstan <andrew@dunslane.net>)
List pgsql-hackers
On Wed, 2007-02-28 at 12:56 -0500, Tom Lane wrote:
> "Sergey E. Koposov" <math@sai.msu.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



pgsql-hackers by date:

Previous
From: Magnus Hagander
Date:
Subject: Removing some of the old VC++ stuff
Next
From: Tom Lane
Date:
Subject: Re: SOC & user quotas