| From: | Rod Taylor <pg(at)rbt(dot)ca> |
|---|---|
| To: | Stephen Frost <sfrost(at)snowman(dot)net> |
| 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:12:21 |
| Message-ID: | 1089385937.15774.68.camel@jester |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> > 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.
I had assumed it would be a directory based quota rather than a user
based one.
> > 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.
Okay. But just so we all know that this means the user with a 5MB quota
could still (potentially) fill 1TB of physical diskspace.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephen Frost | 2004-07-09 15:15:35 | Re: User Quota Implementation |
| Previous Message | Bruce Momjian | 2004-07-09 15:08:46 | Re: pg_dump 7.4 bug |