RLS policies quals/checks are optimized inline, and so I generally avoid writing a separate procedure so the optimizer can do it's thing.
However, if you need a security definer to avoid recursive RLS if you're doing a more complex query say, on a join table, anyone wish there was a flag on the policy itself to specify that `WITH CHECK` or `USING` expression could be run via security definer? The main reason for this is to avoid writing a separate security definer function so you can benefit from the optimizer. Is this possible? Would this be worth a feature request to postgres core? Cheers! Dan
