| From: | Josh Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Greg Stark <stark(at)enterprisedb(dot)com>, Simon Riggs <simon(at)2ndQuadrant(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Should SET ROLE inherit config params? |
| Date: | 2009-03-12 15:26:28 |
| Message-ID: | 200903120826.29273.josh@agliodbs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom,
> Discuss the implications of changing such a GUC partway
> through this sequence. For extra credit, explain what would happen if
> it were set via ALTER ROLE SET for one role or the other.
>
> In short: -1 from me.
Heh. That's your best rejection yet. Someday I'll print out all the
rejection e-mails from you and wallpaper my office. ;-)
I guess what I'm really hoping to do is to hack ROLEs into a primitive
resource management tool. Maybe this is the wrong approach, but we need
*something* in this vein, and from an application development perspective
combining permissions, connections and resource allocation via ROLES makes a
lot of sense. The SET ROLE issue comes in pretty much for login management.
--
Josh Berkus
PostgreSQL
San Francisco
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Berkus | 2009-03-12 15:28:58 | Re: View running statements |
| Previous Message | KaiGai Kohei | 2009-03-12 13:39:01 | Re: Row-Trigger implicitly allows users ACL_SELECT |