| From: | Josh Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | Yann Michel <yann-postgresql(at)spline(dot)de>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: User Quota Implementation |
| Date: | 2005-06-10 17:13:52 |
| Message-ID: | 200506101013.52759.josh@agliodbs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Bruce, Yann,
> Sure. Basically there has not been a lot of interest in this, and we
> are not sure how to implement it without a huge amount of work.
> Considering the other things we are working on, it hasn't been a
> priority, and lots of folks don't like the Oracle approach either.
Yeah. I'd prefer per-database quotas, rather than per-user quotas, which
seem kind of useless. The hard part is making any transaction which
would exceed the per-database quota roll back cleanly with a
comprehensible error message rather than just having the database shut
down.
If we had per-database user quotas, and per-database users, it would pretty
much wind up all of the issues which ISPs have with Postgres.
--
--Josh
Josh Berkus
Aglio Database Solutions
San Francisco
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2005-06-10 17:37:54 | Re: User Quota Implementation |
| Previous Message | Tom Lane | 2005-06-10 17:09:00 | Re: Concrete proposal for large objects and MVCC |