| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, Guillaume LELARGE <guillaume(dot)lelarge(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Something I don't understand with the use of schemas |
| Date: | 2005-12-12 22:27:33 |
| Message-ID: | 439DF955.8050101@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Jim C. Nasby wrote:
>On Mon, Dec 12, 2005 at 05:00:45PM -0500, Tom Lane wrote:
>
>
>>"Jim C. Nasby" <jnasby(at)pervasive(dot)com> writes:
>>
>>
>>>I'd love to see something like SUDO ALTER USER ... SUDO REINDEX ... etc.
>>>That would make it easy to do 'normal' work with a non-superuser
>>>account.
>>>
>>>
>>You can already do most of this with SET/RESET ROLE:
>>
>>
>
>Very cool, I didn't realize that. It would still be nice if there was a
>way to do it on a per-command basis (since often you just need to run
>one command as admin/dba/what-have-you), but I suspect adding that to
>the grammar would be a real PITA. Perhapse it could be added to psql
>though...
>
>
If it's one command can't you wrap it in a security definer function?
cheers
andrew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jim C. Nasby | 2005-12-12 22:35:53 | Re: Something I don't understand with the use of schemas |
| Previous Message | Jim C. Nasby | 2005-12-12 22:12:12 | Re: Something I don't understand with the use of schemas |