How about a trigger that for every say 1000 or 10000 update or inserts (or timely if cron job) will use pg_stats or pg_statistics to decide if a role (user) privileges should be modified to read only (or not)
yes, thats an option but currently the last resort! Doesn't it get difficult to manage so many instances of servers ? Also don't we then need to keep track of different port numbers for each user/group ?
>>> Dev <dev_hyd2001@yahoo.com> wrote: > I have a single Postgres server which will be hosting
multiple > databases belonging to different users. What would be the recommendation to > limit the size of each of the databases?
Have you considered running a different cluster for each user? Each should be run with a different OS user ID, and it would be pretty easy to limit the size of each.
