Replication is a technique for copying the data from one database to another. Supabase uses replication functionality to provide a real-time API. Replication is useful for:
- Spreading out the "load." For example, if your database has a lot of reads, you might want to split it between two databases.
- Reducing latency. For example, you may want one database in London to serve your European customers, and one in New York to serve the US.
Replication is done through publications, a method of choosing which changes to send to other systems (usually another Postgres database). Publications can be managed in the Dashboard or with SQL.
Manage publications in the Dashboard#
- Go to the Database page in the Dashboard.
- Click on Replication in the sidebar.
- Control which database events are sent by toggling Insert, Update, and Delete.
- Control which tables broadcast changes by selecting Source and toggling each table.
Create a publication#
This publication contains changes to all tables.
1create publication publication_name 2for all tables;
Create a publication to listen to individual tables#
1create publication publication_name 2for table table_one, table_two;
Add tables to an existing publication#
1alter publication publication_name 2add table table_name;
1create publication publication_name 2for all tables 3with (publish = 'insert');
1create publication publication_name 2for all tables 3with (publish = 'update');
1create publication publication_name 2for all tables 3with (publish = 'delete');
Remove a publication#
1drop publication if exists publication_name;
Recreate a publication#
If you're recreating a publication, it's best to do it in a transaction to ensure the operation succeeds.
1begin; 2 -- remove the realtime publication 3 drop publication if exists publication_name; 4 5 -- re-create the publication but don't enable it for any tables 6 create publication publication_name; 7commit;