From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
---|---|
To: | Leland Weathers <leland(at)lcweathers(dot)net> |
Cc: | pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: Permission denied on schema for all users on insert to table with fk |
Date: | 2018-07-26 14:19:20 |
Message-ID: | 67f4fb8e-e314-8c08-e13a-08f273fd58d8@aklaver.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 07/26/2018 06:57 AM, Leland Weathers wrote:
>
>
> Before you mentioned a trigger. I am not seeing that in the schema
> you sent. Is there one and if so what is it's definition and that of
> its associated function?
>
>
> I was referring to the "built-in" PostgreSQL system trigger for
> validating fk constraints are met. The trigger that uses the "SELECT 1
> FROM ONLY..." query. That particular query which the logs say I don't
> have permissions to execute is not part of my schema/code.
>
>
> What does show?:
>
> select session_user, current_user;
>
>
> For this particular example, the session_user is: lw, current_user is
> dba (database and schema owner role)
So if I am following neither of these roles have permissions on the
tables. Is that correct?
If you try the INSERT as system_admin, jb or gb does it work?
>
>
> INSERT INTO results.historyitem
> (batchid,datasourceid,sequence_order) VALUES (6,20,1);
>
>
> --
> Adrian Klaver
> adrian(dot)klaver(at)aklaver(dot)com <mailto:adrian(dot)klaver(at)aklaver(dot)com>
>
>
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Charles Clavadetscher | 2018-07-26 14:57:14 | RE: Read only to schema |
Previous Message | Leland Weathers | 2018-07-26 13:57:34 | Re: Permission denied on schema for all users on insert to table with fk |