Re: BUG #14682: row level security not work with partitioned table

From: Joe Conway <mail(at)joeconway(dot)com>
To: Mike Palmiotto <mike(dot)palmiotto(at)crunchydata(dot)com>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Noah Misch <noah(at)leadboat(dot)com>, fte(at)nct(dot)ru, PostgreSQL mailing lists <pgsql-bugs(at)postgresql(dot)org>, Amit Langote <amitlangote09(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: BUG #14682: row level security not work with partitioned table
Date: 2017-06-07 15:45:20
Message-ID: 14a1841e-f5d2-1911-36f4-7ebbd388daa6@joeconway.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-hackers

On 06/07/2017 06:49 AM, Mike Palmiotto wrote:
> I ended up narrowing it down to 4 tables (one parent and 3 partitions)
> in order to demonstrate policy sorting and order of RLS/partition
> constraint checking. It should be much more straight-forward now, but
> let me know if there are any further recommended changes.

Thanks, will take a look towards the end of the day.

Joe

--
Crunchy Data - http://crunchydata.com
PostgreSQL Support for Secure Enterprises
Consulting, Training, & Open Source Development

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Pavel Stehule 2017-06-07 16:39:00 Re: BUG #14694: Long binded parameter value in the postgres log
Previous Message Heikki Linnakangas 2017-06-07 14:48:23 Re: [PATCH] Fixed malformed error message on malformed SCRAM message.

Browse pgsql-hackers by date

  From Date Subject
Next Message Masahiko Sawada 2017-06-07 16:19:14 Re: Challenges preventing us moving to 64 bit transaction id (XID)?
Previous Message Amit Kapila 2017-06-07 15:20:40 Re: statement_timeout is not working as expected with postgres_fdw