From: Scott Marlowe <scott.marlowe@gmail.com>
To: pronix pronix <pronix.service@gmail.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: how i can restrict databaseusers ?
Date: Tue, 20 May 2008 11:38:38 -0600
Message-ID: <dcc563d10805201038v2dade65cg306824a8377df295@mail.gmail.com> (raw)
In-Reply-To: <639ce0480805200657l82cd49coe381814a2d86c655@mail.gmail.com>
References: <639ce0480805200657l82cd49coe381814a2d86c655@mail.gmail.com>
On Tue, May 20, 2008 at 7:57 AM, pronix pronix <pronix.service@gmail.com> wrote:
> hello
> how i can restrict dbusers ( user's db size, cpu time)?
> how i can monitoring this parameters
You can create table spaces for each user, and then create a db or
schema or whatnot in that tablespace. If each tablespace is on a
partition that is limited to some size, then you've limited the user's
space. You don't get the more fine grained quotas that dbs like
Oracle provide, but then again, since you're not spending $250,000 a
year licensing postgresql, I guess you can buy a lot more space for
the users to play in if they all share the same db.
As for CPU time, there's really not restriction by user capability in
postgresql at this time.
To monitor it you can turn on stats collection and track what
statements are using up the most CPU by pid.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: scott.marlowe@gmail.com, pronix.service@gmail.com
Subject: Re: how i can restrict databaseusers ?
In-Reply-To: <dcc563d10805201038v2dade65cg306824a8377df295@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox