Performance Advisor : Warnings on RLS

RLS

We have many of these warnings;

Table public.[table] has a row level security policy [policy_name] that re-evaluates current_setting() or auth.<function>() for each row. This produces suboptimal query performance at scale. Resolve the issue by replacing auth.<function>() with (select auth.<function>()). See docs for more info.

Table public.[table] has a row level security policy [policy_name] that re-evaluates current_setting() or auth.<function>() for each row. This produces suboptimal query performance at scale. Resolve the issue by replacing auth.<function>() with (select auth.<function>()). See docs for more info.

With our current product ecosystem we aren't entirely using Supabase auth "although I wish we were, not my decision" and Supabase doesn't fully support WorkOS in the way we needed "can't remember what/why, was a while back". We still have WorkOS setup as a third-party auth service though and can access the usual

auth.uid()

auth.uid()

via

auth.jwt() ->> 'sub'

auth.jwt() ->> 'sub'

when we need this, our setup does not create any

auth.users

auth.users

fyi.

All of the policies or any other queries are set with

(select auth.jwt() ->> 'sub')

(select auth.jwt() ->> 'sub')

and still getting these warnings, are these false positives?

Supabase•2mo ago•

5 replies

c.garrison

Performance Advisor : Warnings on RLS

RLS

We have many of these warnings;

Table public.[table] has a row level security policy [policy_name] that re-evaluates current_setting() or auth.<function>() for each row. This produces suboptimal query performance at scale. Resolve the issue by replacing auth.<function>() with (select auth.<function>()). See docs for more info.

Table public.[table] has a row level security policy [policy_name] that re-evaluates current_setting() or auth.<function>() for each row. This produces suboptimal query performance at scale. Resolve the issue by replacing auth.<function>() with (select auth.<function>()). See docs for more info.

auth.uid()

auth.uid()

via

auth.jwt() ->> 'sub'

auth.jwt() ->> 'sub'

when we need this, our setup does not create any

auth.users

auth.users

fyi.

All of the policies or any other queries are set with

(select auth.jwt() ->> 'sub')

(select auth.jwt() ->> 'sub')

and still getting these warnings, are these false positives?

Performance Advisor : Warnings on RLS

Similar Threads

Performance Advisor : Warnings on RLS

Similar Threads

Similar Threads

Similar Threads