| From: | Matt Warner <matt(at)warnertechnology(dot)com> |
|---|---|
| To: | Bosco Rama <postgres(at)boscorama(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Unprivileged access to pgsql functions? |
| Date: | 2011-03-04 21:58:49 |
| Message-ID: | AANLkTi=APhfFFU=kRMURe8ri91dOLKZfEb8AR2buH-8f@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Fri, Mar 4, 2011 at 1:56 PM, Bosco Rama <postgres(at)boscorama(dot)com> wrote:
> Matt Warner wrote:
> >
> > The function cannot be defined in the user's DB because "language C" is
> > considered a security risk, so only the superuser can do that. Or that's
> > what I get from reading anyway...
>
> psql -U postgres -d user_db
>
> will allow the superuser to then define the function in the user's DB.
>
> Once there, you can grant access, if needed.
>
> Bosco.
>
Success! Too much exposure to Oracle had me forgetting that the databases
are separate in Postgres. D'oh!
Thank you very much!
Matt
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Aleksey Tsalolikhin | 2011-03-04 22:03:23 | Re: database is bigger after dump/restore - why? (60 GB to 109 GB) |
| Previous Message | Matt Warner | 2011-03-04 21:57:19 | Re: Unprivileged access to pgsql functions? |