title |
---|
Azure Flexible Server Postgres Source Setup Guide |
import SSHTunnel from '/snippets/ssh-tunnel.mdx';
Anything on or after Postgres 12
You don't need to follow the below steps if the settings wal_level
. This setting should mostly be pre-configured if you are migrating from another data replication tool.
- Click on the Server parameters section
- Edit the
wal_level
tological
- This change would require a server restart. So restart when requested.
If you are using PeerDB Cloud, please follow the below steps to add peerdb ips to your network.
- Go to the Networking tab and add the public IPs of your PeerDB Cloud instance to the Firewall
Connect to your Azure Flexible Server Postgrees through the admin user and run the below commands:
-
Create a Postgres user for exclusively PeerDB.
-
CREATE USER peerdb_user PASSWORD 'some-password';
-
-
Provide read-only access to the schema from which you are replicating tables to the
peerdb-user
. Below example shows setting up permissions for thepublic
schema. If you want to grant access to multiple schemas, you can run these three commands for each schema.-
GRANT USAGE ON SCHEMA "public" TO peerdb_user; GRANT SELECT ON ALL TABLES IN SCHEMA "public" TO peerdb_user; ALTER DEFAULT PRIVILEGES IN SCHEMA "public" GRANT SELECT ON TABLES TO peerdb_user;
-
-
Grant replication access to this user:
-
ALTER ROLE peerdb_user REPLICATION;
-
-
Create a publication that you'll be using for creating the MIRROR (replication) in future.
-
CREATE PUBLICATION peerdb_publication FOR TABLE table1, table2, table3....;
-
-
Set
wal_sender_timeout
to 0 forpeerdb_user
ALTER ROLE peerdb_user SET wal_sender_timeout to 0;
Through the PeerDB UI, create the Flexible Postgres Peer using the peerdb_user
that you created in the previous step.