From: | Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at> |
---|---|
To: | "'Jorge Torralba *EXTERN*'" <jorge(dot)torralba(at)gmail(dot)com> |
Cc: | Wei Shan *EXTERN* <weishan(dot)ang(at)gmail(dot)com>, "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: Schema Consolidation in PostgreSQL |
Date: | 2015-05-11 07:14:11 |
Message-ID: | A737B7A37273E048B164557ADEF4A58B3660E403@ntex2010i.host.magwien.gv.at |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Jorge Torralba wrote:
> On Sun, May 10, 2015 at 3:01 AM, Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at> wrote:
>> Wei Shan wrote:
>>> When I say resource manager, I actually meant if there's a way to ensure the maximum
>>> resource utilization by a certain user. For example in Oracle, we can actually limit
>>> a certain user by setting a resource plan on it. Resource can be CPU.
>> There is no such thing in PostgreSQL.
>> You can limit the storage a user can use by keeping his data in a table space with a certain size.
> You can to some extent do the following
>
> ALTER USER name SET configuration_parameter { TO | = } { value | DEFAULT }
But that won't limit the resources used by a user.
A user can have several connections.
You could maybe limit memory usage somewhat by setting work_mem low for
a user and limiting their connections with
ALTER ROLE ... CONNECTION LIMIT ...
But that's a big step from something like Oracle's Resource Manager.
Yours,
Laurenz Albe
From | Date | Subject | |
---|---|---|---|
Next Message | Muthusamy, Sivaraman | 2015-05-11 13:51:33 | How to VACUUM_FULL / clean / truncate of pg_largeobject without (much) downtime? |
Previous Message | Jorge Torralba | 2015-05-10 15:22:43 | Re: Schema Consolidation in PostgreSQL |