| From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
|---|---|
| To: | Daniel Gallo <danielito(dot)gallo(at)gmail(dot)com>, "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
| Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: How Restricting user |
| Date: | 2016-02-25 18:38:42 |
| Message-ID: | 56CF4A32.7060800@commandprompt.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 02/25/2016 10:09 AM, Daniel Gallo wrote:
> thanks a lot David!!!!
It wouldn't be hard to create a limiting system in user space however.
It would be a little obnoxious but it can be done. For example
connect_time and idle_time are relatively easy to implement with a
proper session handler in user space. You could also invalidate user
accounts by using the valuntil flag in pg_user.
It would be harder to do things like cpu_per_call (the database isn't
really the place for that) as well as logical reads.
Sincerely,
JD
--
Command Prompt, Inc. http://the.postgres.company/
+1-503-667-4564
PostgreSQL Centered full stack support, consulting and development.
Everyone appreciates your honesty, until you are honest with them.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | dangal | 2016-02-25 18:55:03 | Re: How Restricting user |
| Previous Message | Daniel Gallo | 2016-02-25 18:09:24 | Re: How Restricting user |