Re: Best way to limit database sizes

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)

Cheers
Medi

On Thu, Jul 3, 2008 at 10:48 AM, Dev <dev_hyd2001(at)yahoo(dot)com> wrote:

> 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
>
>
> --- On *Thu, 7/3/08, Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>* wrote:
>
> From: Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>
> Subject: Re: [ADMIN] Best way to limit database sizes
> To: pgsql-admin(at)postgresql(dot)org, dev_hyd2001(at)yahoo(dot)com
> Date: Thursday, July 3, 2008, 6:28 PM
>
> >>> Dev <dev_hyd2001(at)yahoo(dot)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.
>
> -Kevin
>
>
>