Leandro Pereira cd5935d3e2 docs(realtime): schema restriction (#48157) ...

## I have read the
[CONTRIBUTING.md](https://github.com/supabase/supabase/blob/master/CONTRIBUTING.md)
file.

YES

## What kind of change does this PR introduce?

Make it clear what users can and can't do on `realtime` schema.

## What is the current behavior?

After https://github.com/supabase/realtime/pull/1993 creating or
altering the realtime schema is no longer allowed, but some users are
still trying to execute `ALTER TABLE realtime.messages ENABLE ROW LEVEL
SECURITY` or trying to create objects on that schema.

<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit

* **Documentation**
* Clarified Realtime schema protections, including a caution about how
the `realtime` schema is restricted and what permission errors to expect
when creating objects there.
* Confirmed that row level security is enabled by default on
`realtime.messages`, and that managing its RLS policies is supported.
* Documented the additional binary-capable function,
`realtime.send_binary`, alongside the existing `realtime.send` behavior.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->

2026-07-21 13:19:56 -04:00

..

_partials

feat(pipelines): Update product docs and UI copy (#47997)

2026-07-17 11:43:04 +02:00

guides

docs(realtime): schema restriction (#48157)

2026-07-21 13:19:56 -04:00

troubleshooting

docs: clarify edge function deployment size limits (5MB server-side vs 20MB local) (#47941)

2026-07-15 06:54:19 -06:00

navigation.references.ts

docs: wire @supabase/server v1 into the reference pipeline (#47570)

2026-07-07 17:08:51 +03:00