Postgres Pro
Downloads
Home   >   mailing lists

Re: Limiting user from changing its own attributes - Mailing list pgsql-general

From David G. Johnston
Subject Re: Limiting user from changing its own attributes
Date
Msg-id CAKFQuwYZL6TkeEmDT4xZ9F2X2179pM-cg1w-qbr9hqXqgX8Q+Q@mail.gmail.com
Whole thread Raw
In response to Re: Limiting user from changing its own attributes  (Sameer Kumar <sameer.kumar@ashnik.com>)
Responses Re: Limiting user from changing its own attributes
List pgsql-general
Tree view
On Friday, April 10, 2015, Sameer Kumar <sameer.kumar@ashnik.com> wrote:
On Sat, Apr 11, 2015 at 12:57 AM David G. Johnston <david.g.johnston@gmail.com> wrote:
On Fri, Apr 10, 2015 at 9:01 AM, Sameer Kumar <sameer.kumar@ashnik.com> wrote:

Yes either an upper bound to which users can set their own values to.
 
Upper is somewhat easier but currently the system would only recognize a global constraint.

Does it? Even though my work_mem in postgresql.conf is 1MB, the user can alter itself to set its own work_mem to 1GB. Or did I interpret your statement wrongly?


Pg_settings currently has an upper bound column - though it is a view and that value cannot be changed that I know of.  But if it could I suspect that whatever catalog you would change to affect it would only cause a global change.  There is no alter database, role, or postgresql way to change that value.

 David J.

pgsql-general by date:

Previous
From: Sameer Kumar
Date:
Subject: Re: Limiting user from changing its own attributes
Next
From: Edson Carlos Ericksson Richter
Date:
Subject: Has anyone used C-JDBC, HA-JDBC or SymmetricDB with PostgreSQL?