From: | "Jonah H(dot) Harris" <jharris(at)tvi(dot)edu> |
---|---|
To: | Yann Michel <yann-postgresql(at)spline(dot)de> |
Cc: | Josh Berkus <josh(at)agliodbs(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: User Quota Implementation |
Date: | 2005-06-13 22:47:20 |
Message-ID: | 42AE0CF8.1060904@tvi.edu |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Well... a maximum tablespace size would be much easier to implement and
would still accomplish this level of quota for larger organizations and
database systems.
I vote for implmenting the maximum tablespace size and revisiting actual
user/group quotas when the need arises.
Was someone going to implement this? If not, I can probably get it done
in a couple days.
-Jonah
Yann Michel wrote:
> Hi Josh, hi jonah,
>
> On Mon, Jun 13, 2005 at 12:36:12PM -0700, Josh Berkus wrote:
>
>>>Don't get me wrong, I think we need tablespace maximums. What I'm
>>>looking at is a user/group-based quota which would allow a superuser to
>>>grant say, 2G of space to a user or group. Any object that user owned
>>>would be included in the space allocation.
>>>
>>>So, if the user owns three tablespaces, they can still only have a
>>>maximum of 2G total. This is where I think it would be wise to allow
>>>the tablespace owner and/or superuser to set the maximum size of a
>>>tablespace.
>>
>>Yeah, the problem is that with the upcoming "group ownership" I see
>>user-based quotas as being rather difficult to implement unambiguously.
>>Even more so when we get "local users" in the future. So I'd only want
>>to do it if there was a real-world use case that tablespace quotas
>>wouldn't satisfy.
>
>
> Well, I think in one way jona is right, that I mixed up two things.
> Indeed a max size for a tablespace is something different, than a quota.
> In my opinion, it makes only sense to use quotas for ressource-owners on
> ressources, i.e. tablespaces. To as an example I think about some
> tablespace whith a MAXSIZE of 2 GB (that it won't grow until the disk is
> full) and a QUOTA of 500 MB for user A on that certain tablespace. In
> general (of cause this is only my experience in using quotas in dbms)
> you will create different tablespaces for different object kinds/types
> i.e. one for indexes, one for dimensions and at least one for the fact
> data in a dwh. So to allow users to store their comparable tables in the
> appropriate tablespace you'd set up a quota for them.
>
>
> Regards,
> Yann
--
Jonah H. Harris, UNIX Administrator | phone: 505.224.4814
Albuquerque TVI | fax: 505.224.3014
525 Buena Vista SE | jharris(at)tvi(dot)edu
Albuquerque, New Mexico 87106 | http://w3.tvi.edu/~jharris/
A hacker on a roll may be able to produce, in a period of a few
months, something that a small development group (say, 7-8 people)
would have a hard time getting together over a year. IBM used to
report that certain programmers might be as much as 100 times as
productive as other workers, or more.
-- Peter Seebach
From | Date | Subject | |
---|---|---|---|
Next Message | Jonah H. Harris | 2005-06-13 22:48:33 | Re: [HACKERS] mirroring oracle database in pgsql |
Previous Message | Sean Davis | 2005-06-13 22:34:49 | Re: [HACKERS] mirroring oracle database in pgsql |