Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 3C768650E82 for ; Thu, 3 Jul 2008 15:31:48 -0300 (ADT) Received: from postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 76369-06 for ; Thu, 3 Jul 2008 15:31:42 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from an-out-0708.google.com (an-out-0708.google.com [209.85.132.251]) by postgresql.org (Postfix) with ESMTP id D35EA64FD64 for ; Thu, 3 Jul 2008 15:31:43 -0300 (ADT) Received: by an-out-0708.google.com with SMTP id d30so204705and.33 for ; Thu, 03 Jul 2008 11:31:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type:references; bh=qQkpHnlMQXmT4PFLXkp+FQk0JFqCV5a8qFx5YN/vJZQ=; b=jcqIUH8JUvfxDjRwJVJEkrQWQ37UXEbuvP7h5bFb/APndf7w1e3Jk1mAqSeUCs5RCv /+iuJa2Synxyco2ATk0p/yToywX7SKY/M/K7xbL0UEOmaj9P42hr9jN5k+kSZRuSHAvq B2RN7v82Coo1JqVMMTaitYKAHAZKF+9GRcg5Q= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:references; b=hv7TAcSIH3OTy2diWQ+tvqTof6JOKkBHRzVtyrCPKC2WDJoZBzdvV7+vhnq26NHK3N EfY/r9U6y46qfMR7zGgIJjqdllwwVMlc/QpfFKOwpcM2qNlN0rvHng0XMh7thBPU8xLQ fY74abk+w/zEykm7Q4DB7548jisUv8KmlZjhA= Received: by 10.100.46.10 with SMTP id t10mr74708ant.22.1215109902095; Thu, 03 Jul 2008 11:31:42 -0700 (PDT) Received: by 10.100.190.19 with HTTP; Thu, 3 Jul 2008 11:31:41 -0700 (PDT) Message-ID: <8078a1730807031131i79bea3ffpdaa03233afac7c57@mail.gmail.com> Date: Thu, 3 Jul 2008 11:31:41 -0700 From: Montaseri To: dev_hyd2001@yahoo.com Subject: Re: Best way to limit database sizes Cc: pgsql-admin@postgresql.org In-Reply-To: <869366.20954.qm@web53708.mail.re2.yahoo.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_10538_12690975.1215109902047" References: <486CB7E4.EE98.0025.0@wicourts.gov> <869366.20954.qm@web53708.mail.re2.yahoo.com> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200807/45 X-Sequence-Number: 29655 ------=_Part_10538_12690975.1215109902047 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline 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 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 * wrote: > > From: Kevin Grittner > Subject: Re: [ADMIN] Best way to limit database sizes > To: pgsql-admin@postgresql.org, dev_hyd2001@yahoo.com > Date: Thursday, July 3, 2008, 6:28 PM > > >>> Dev 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 > > > ------=_Part_10538_12690975.1215109902047 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline 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@yahoo.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.Grittner@wicourts.gov> wrote:
From: Kevin Grittner <Kevin.Grittner@wicourts.gov>
Subject: Re: [ADMIN] Best way to limit database sizes
To: pgsql-admin@postgresql.org, dev_hyd2001@yahoo.com
Date: Thursday, July 3, 2008, 6:28 PM


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

 
-Kevin


------=_Part_10538_12690975.1215109902047--