Re: Schema Consolidation in PostgreSQL

From: Jorge Torralba <jorge(dot)torralba(at)gmail(dot)com>
To: Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at>
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-10 15:22:43
Message-ID: CACut7uQL63HY1Qh=djbq7WHdDivG6ftBipqDonD+8N3Zz4LRsg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

You can to some extent do the following

ALTER USER name SET configuration_parameter { TO | = } { value | DEFAULT }
ALTER USER name SET configuration_parameter FROM CURRENT
ALTER USER name RESET configuration_parameter

configuration_parameter
value

Set this role's session default for the specified configuration
parameter to the given value. If value is DEFAULT or, equivalently,
RESET is used, the role-specific variable setting is removed, so the
role will inherit the system-wide default setting in new sessions. Use
RESET ALL to clear all role-specific settings. SET FROM CURRENT saves
the session's current value of the parameter as the role-specific
value. If IN DATABASE is specified, the configuration parameter is set
or removed for the given role and database only.

Role-specific variable settings take effect only at login; SET ROLE
<http://www.postgresql.org/docs/9.3/static/sql-set-role.html> and SET
SESSION AUTHORIZATION
<http://www.postgresql.org/docs/9.3/static/sql-set-session-authorization.html>
do not process role-specific variable settings.

See SET <http://www.postgresql.org/docs/9.3/static/sql-set.html> and
Chapter 18 <http://www.postgresql.org/docs/9.3/static/runtime-config.html>
for more information about allowed parameter names and values.

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.
>
> Yours,
> Laurenz Albe
>
> --
> Sent via pgsql-admin mailing list (pgsql-admin(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-admin
>

--
Thanks,

Jorge Torralba
----------------------------

Note: This communication may contain privileged or other confidential
information. If you are not the intended recipient, please do not print,
copy, retransmit, disseminate or otherwise use the information. Please
indicate to the sender that you have received this email in error and
delete the copy you received. Thank You.

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Albe Laurenz 2015-05-11 07:14:11 Re: Schema Consolidation in PostgreSQL
Previous Message Albe Laurenz 2015-05-10 10:01:22 Re: Schema Consolidation in PostgreSQL