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:content-transfer-encoding:content-disposition:references;
	b=wENLzrWbnjPYV0/5V3Ztip9qmGaLjrZ/f39gYBdaNBZaJqkPmqI6r2nZsDqVpJtbyHuGBg4IIxX2rbu8B5jmmc1JllPXhunFGsqKCKd/OYgW6C9shU0pFX0yp+H4gT6Xe/9oJ/Y46gt2CXnxZ/y2fkh1jkqLmcRkGoQ84zfUHkw=
Message-ID: <dcc563d10805201038v2dade65cg306824a8377df295@mail.gmail.com>
Date: Tue, 20 May 2008 11:38:38 -0600
From: "Scott Marlowe" <scott.marlowe@gmail.com>
To: "pronix pronix" <pronix.service@gmail.com>
Subject: Re: how i can restrict databaseusers ?
Cc: pgsql-admin@postgresql.org
In-Reply-To: <639ce0480805200657l82cd49coe381814a2d86c655@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
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.