Hello Jim,
Your approach of using table inheritance in PostgreSQL for implementing
row-level security (RLS) has some interesting aspects, but there are
potential pitfalls and alternatives that you should consider. Below,
I'll outline some key points to
Table Inheritance and Perfor
Hi,
I'm trying to implement a system which requires row level security on
some key data tables (most do not require RLS). The data tables will
grow substantially (rows likely > +100M/year - the system is > 80% data
insert plus < 20% updates and by design, no deletes).
So
On Sunday, October 11, 2020, Gopisetty, Ramesh
wrote:
>
> to sch USING ( key =
> f_sel_1(key)
> );
>
As Tom said it doesn’t matter what you classify the function as (stable,
etc) if your function call accepts a column reference as an input and
compares its output to another colu
AM
To: Gopisetty, Ramesh
Cc: pgsql-performance@lists.postgresql.org
Subject: Re: Performance issue when we use policies for Row Level Security
along with functions
"Gopisetty, Ramesh" writes:
> Policy
> create policy policy_sel on test FOR SELECT to ram1 USING ( testkey in
&
"Gopisetty, Ramesh" writes:
> Policy
> create policy policy_sel on test FOR SELECT to ram1 USING ( testkey in
> (f_sel_policy_test(testkey)) );
> Going to a Sequential scan instead of index scan. Hence, performance issue.
> If i replace the policy with stright forward without function then
De: "Gopisetty, Ramesh"
Para: "pgsql-performance"
Enviadas: Quarta-feira, 16 de setembro de 2020 0:39:08
Assunto: Performance issue when we use policies for Row Level Security along
with functions
BQ_BEGIN
Hi,
I'm seeing a strange behavior when we im
Hi,
I'm seeing a strange behavior when we implement policies (for RLS - Row level
security) using functions.
table test consists of columns testkey,oid,category,type,description...
Policy
create policy policy_sel on test FOR SELECT to ram1 USING ( testkey in
(f_sel_policy_test(te
