Re: Postgres trigger side-effect is occurring out of order withrow-level security select policy
От | Charles Clavadetscher (SwissPUG) |
---|---|
Тема | Re: Postgres trigger side-effect is occurring out of order withrow-level security select policy |
Дата | |
Msg-id | af2735ba-656d-44bf-904f-95bccdf9f418@getmailbird.com обсуждение исходный текст |
Ответ на | Re: Postgres trigger side-effect is occurring out of order withrow-level security select policy (Adrian Klaver <adrian.klaver@aklaver.com>) |
Ответы |
Re: Postgres trigger side-effect is occurring out of order withrow-level security select policy
(Carl Sverre <sverre.carl@gmail.com>)
|
Список | pgsql-general |
On 30.09.2018 23:31:32, Adrian Klaver <adrian.klaver@aklaver.com> wrote:On 9/30/18 1:13 PM, Carl Sverre wrote:
> Thanks for the initial results. Can you check that you are not using
> super permissions and are enabling row security when running the test?
> Super ignores row security.
Yeah, big oops on my part, I was running as superuser. Running as
non-superuser resulted in the failure you see. I tried to get around
this with no success. My suspicion is that the new row in b is not
visible to the returning(SELECT) query in a until after the transaction
completes. Someone with more knowledge on this then I will have to
confirm/deny my suspicion.
>
> Also yes, I forgot to add the policy names, sorry about that.
> On Sun, Sep 30, 2018 at 1:34 AM Charles Clavadetscher (SwissPUG)
> > wrote:
>
> Hello
--
Adrian Klaver
adrian.klaver@aklaver.com
В списке pgsql-general по дате отправления:
Следующее
От: Carl SverreДата:
Сообщение: Re: Postgres trigger side-effect is occurring out of order withrow-level security select policy