Files
supabase/apps/docs/components/Navigation
Miranda LimonczenkoandClaude Opus 5 1ae99901a4 docs(database): split RLS tuning into its own guide
The RLS guide spent 225 lines and 5 benchmark tables on performance,
covering the same six tips as the RLS Performance and Best Practices
troubleshooting entry, from the same source.

- Add guides/database/postgres/row-level-security-performance. Carries
  the client-filter and join-rewrite rules, all 5 benchmark tables
  merged into one, and a diagnostic section the guide never had: toggle
  RLS off to confirm it's the cost, then read the plan under an
  impersonated role.
- Keep every eval-graded rule on the RLS guide. Indexes, select-wrapping,
  role scoping, and security definer safety are correctness rules, not
  tuning tips, and an agent reading the guide top-down has to reach them.
  Group the first three under "Write policies that scale".
- Repoint the Grafana IO troubleshooting entry at the new page.
- Rewrite More resources as Related content. Each link now says what it
  is. Drops discussion 14576: locked, mislabeled here as "RLS Guide and
  Best Practices", and superseded by the troubleshooting entry.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-12 16:16:02 -07:00
..
2025-11-17 08:39:13 -07:00