Now you can use Realtime Broadcast to scale database changes sent to clients with Broadcast from Database. You can use Supabase Realtime build immersive features like notifications, chats, live cursors, shared whiteboards, multiplayer games, and listen to Database changes. Broadcasting from the Database is our latest improvement that offers more benefits than Postgres Changes, including targeting specific actions, choosing which columns to send in the body of the message, and using SQL to selectively send data to specific channels. You now have two options for building real-time applications using database changes: Broadcast from Database, which sends messages triggered by changes within the Database itself, and Postgres Changes, polling the Database for changes. The former is suitable for applications with many connected users, sanitizing the payload of a message, or reducing latency of sent messages. To set up Broadcast from Database, you need to set up Row-Level Security policies, create a function that will be called whenever a Database change is detected, and set up trigger conditions under which you will execute the function. Finally, you need to set up your client code to listen for changes. Realtime Broadcast from Database sets up a replication slot against a publication created for the `realtime.messages` table, letting Realtime listen for Write Ahead Log (WAL) changes whenever new rows are inserted. It broadcasts that message to the target channel right away and uses helper functions like `realtime.send` and `realtime.broadcast_changes` to create payloads similar to Postgres Changes. This enables new uses like broadcasting directly from Database functions, sending only specific fields to connected clients, and creating scheduled events using Supabase Cron.