James Robinson wrote:
On Jul 9, 2004, at 12:04 PM, Jonah H. Harris wrote:
- Quota acts on any object owned by the user. Is this adequate for everyone?
Does changing owner also trigger new quota calculations on both the new and old owner?
Quota calculations are performed per-owner at commit time. As only a superuser can perform an ALTER TABLE OWNER, my implementation allows quotas to be handled automatically at run-time for the current-owner. Therefore, there is no need to perform new calculations for each user. I'm still testing large objects.
Is there any additional functionality you would like to see in a quota implementation?
Quotas per user per tablespace, assuming 7.5 gets tablespaces.
I agree.
User quotas would make postgres on a shared university box much more pleasant.
Oh yeah! Our college is using PostgreSQL for student user accounts, which is why I originally implemented this :).
---- James Robinson Socialserve.com
-- Jonah H. Harris, UNIX Administrator | phone: 505.224.4814 Albuquerque TVI | fax: 505.224.3014 525 Buena Vista SE | [EMAIL PROTECTED] Albuquerque, New Mexico 87106 | http://w3.tvi.edu/~jharris/
"All great truths begin as blasphemies."
-- George Bernard Shaw
---------------------------(end of broadcast)--------------------------- TIP 9: the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
