| From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
|---|---|
| To: | rajan <vgmonnet(at)gmail(dot)com> |
| Cc: | "pgsql-general(at)postgresql(dot)org >> PG-General Mailing List" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Unable to select a table as postgres user |
| Date: | 2015-10-30 07:17:04 |
| Message-ID: | CAFj8pRBVdz0wWa89GyeHctuNvH=fvAyRVEd=A=ZEg6h1H_Lg8A@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
2015-10-30 7:56 GMT+01:00 rajan <vgmonnet(at)gmail(dot)com>:
> Yes. I agree that the superuser cannot be restricted with any access.
>
> But my scenarios is, I am executing a function(VOLATILE SECURITY DEFINER)
> using the superuser and it function fails with unable to select a
> particular
> table.
>
who owns this function?
>
> At the same time, I am able to select the table as a superuser, by
> executing
> select * from table_name;
>
>
>
> --
> View this message in context:
> http://postgresql.nabble.com/Unable-to-select-a-table-as-postgres-user-tp5872036p5872041.html
> Sent from the PostgreSQL - general mailing list archive at Nabble.com.
>
>
> --
> Sent via pgsql-general mailing list (pgsql-general(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-general
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Charles Clavadetscher | 2015-10-30 07:22:03 | Re: Unable to select a table as postgres user |
| Previous Message | rajan | 2015-10-30 06:56:56 | Re: Unable to select a table as postgres user |