| From: | Stephen Frost <sfrost(at)snowman(dot)net> |
|---|---|
| To: | Rod Taylor <pg(at)rbt(dot)ca> |
| Cc: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>, "Jonah H(dot) Harris" <jharris(at)tvi(dot)edu>, PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: User Quota Implementation |
| Date: | 2004-07-09 15:06:50 |
| Message-ID: | 20040709150650.GE21419@ns.snowman.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
* Rod Taylor (pg(at)rbt(dot)ca) wrote:
> I would think having would allow us to take advantage of all of the
> various kernel level filesystem features without needing to implement
> them directly within PostgreSQL (crypto, quotas, data mirror, etc.).
>
> Simply setup a tablespace for a given user with permissions to allow
> only that user to create new objects within it and make it the default
> location) -- tie their schema to their tablespace? -- then set a kernel
> level quota on their tablespace.
Since the user accessing/writing to the tablespaces would be the
postgres user I don't really think this 'solution' works in reality.
> Or do we expect a PostgreSQL implementation to do more than that, to
> only count active data by ignoring data pending a vacuum?
Certainly, it should.
Stephen
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2004-07-09 15:08:46 | Re: pg_dump 7.4 bug |
| Previous Message | Rod Taylor | 2004-07-09 14:19:16 | Re: User Quota Implementation |