| From: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com> |
|---|---|
| To: | Jon Erdman <postgresql(at)thewickedtribe(dot)net> |
| Cc: | Phil Sorber <phil(at)omniti(dot)com>, Craig Ringer <craig(at)2ndquadrant(dot)com>, Stephen Frost <sfrost(at)snowman(dot)net>, PostgreSQL-development Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: My first patch! (to \df output) |
| Date: | 2013-01-25 15:26:37 |
| Message-ID: | 5102A42D.5040806@vmware.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 23.01.2013 07:31, Jon Erdman wrote:
> Done. Attached.
Thanks, committed.
On 29.12.2012 20:56, Stephen Frost wrote:
> No biggie, and to get the bike-shedding started, I don't really like the
> column name or the values.. :) I feel like something clearer would be
> "Runs_As" with "caller" or "owner".. Saying "Security" makes me think
> of ACLs more than what user ID the function runs as, to be honest.
I have to agree that calling the property "security definer/invoker" is
a poor name in general. "security" is such on overloaded word that it
could mean anything. "Run as" would make a lot more sense. But given
that that's the nomenclature we have in the CREATE FUNCTION statement,
the docs, prosecdef column name and everywhere, that's what we have to
call it in \df+ too.
- Heikki
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2013-01-25 15:28:16 | Re: Hanging backends and possible index corruption |
| Previous Message | Peter Eisentraut | 2013-01-25 15:26:10 | Re: BUG #6510: A simple prompt is displayed using wrong charset |