From: | Andrzej Pilacik <cypisek77(at)gmail(dot)com> |
---|---|
To: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
Cc: | Stephen Frost <sfrost(at)snowman(dot)net>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: Strange security issue with Superuser access |
Date: | 2015-03-10 15:20:59 |
Message-ID: | CAJw8uJSFRH=rRuWAzBCu84p2pNUGyQcHQxD9XoopvixPsCiZzA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
I see the issues that this person might be having. I am not doing a
restore or working on an existing issue.
My setup is very vanilla, anyone can create these tables and test, will get
the same permission error... (I did it in a brand new environment)
What I am asking here is why does a SUPERUSER not able to insert the data
when the constraint is introduced.
On Tue, Mar 10, 2015 at 10:16 AM, Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
wrote:
> On 03/10/2015 05:41 AM, Stephen Frost wrote:
>
>> * Andrzej Pilacik (cypisek77(at)gmail(dot)com) wrote:
>>
>>> Can anyone explain how the FK constraint function works? Is it executed
>>> as
>>> the owner of the object. That is the only thing that would make sense
>>> for
>>> me.
>>>
>>
>> Yes.
>>
>
>
> This brought back a memory. For the hows and whys see this thread :
>
> http://www.postgresql.org/message-id/4D6BB33F.9010704@lupomesky.cz
>
>
>> Thanks,
>>
>> Stephen
>>
>>
>
> --
> Adrian Klaver
> adrian(dot)klaver(at)aklaver(dot)com
>
From | Date | Subject | |
---|---|---|---|
Next Message | David G. Johnston | 2015-03-10 15:27:47 | Re: Strange security issue with Superuser access |
Previous Message | Jim Nasby | 2015-03-10 15:11:08 | Re: Postgres and data warehouses |