> > 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.