* Rod Taylor ([EMAIL PROTECTED]) 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
signature.asc
Description: Digital signature
