Anything on or after Postgres 12
You don’t need to follow the below steps if wal_level
is set to logical
. This setting should mostly be pre-configured if you are migrating from another data replication tool.
Server Parameters
wal_level
to logical
Change wal_level to logical
Restart server
Connect to your Azure Flexible Server Postgres through the admin user and run the below commands:
Create a Postgres user for exclusively PeerDB.
Provide read-only access to the schema from which you are replicating tables to the peerdb_user
. Below example shows setting up permissions for the public
schema. If you want to grant access to multiple schemas, you can run these three commands for each schema.
Grant replication access to this user:
Create publication that you’ll be using for creating the MIRROR (replication) in future.
Set wal_sender_timeout
to 0 for peerdb_user
The PeerDB user must not be restricted by RLS policies, as it can lead to missing data. You can disable RLS policies for the user by running the below command:
Sometimes to connect to your Postgres database you may need PeerDB to use an SSH tunnel.
This is typically used when your database is not publicly accessible and you need to connect to it a jump server in your VPC.
This is done by creating an SSH tunnel to your jump server and then connecting to the database through the tunnel. All of this is handled by PeerDB natively.
Generate a key-pair
Generate a key-pair using the following command:
This will generate a private key (peerdb_key.pem
) and a public key (peerdb_key.pub
).
Add public key to your jump server
Add the public key to your jump server. This can be done by adding the public key to the ~/.ssh/authorized_keys
file on the jump server.
Add private key to the connection
When creating a Postgres peer you can specify the option to use an SSH tunnel. There you will be able to provide the private key you generated in the first step along with the jump server details.
If you are using PeerDB Cloud, please follow the below steps to add peerdb ips to your network.
Add PeerDB IPs to Firewall
Through the PeerDB UI, create the Flexible Postgres Peer using the peerdb_user
that you created in the previous step.
Choose PostgreSQL Peer
Peer Creation and Validation
Created Peer
Anything on or after Postgres 12
You don’t need to follow the below steps if wal_level
is set to logical
. This setting should mostly be pre-configured if you are migrating from another data replication tool.
Server Parameters
wal_level
to logical
Change wal_level to logical
Restart server
Connect to your Azure Flexible Server Postgres through the admin user and run the below commands:
Create a Postgres user for exclusively PeerDB.
Provide read-only access to the schema from which you are replicating tables to the peerdb_user
. Below example shows setting up permissions for the public
schema. If you want to grant access to multiple schemas, you can run these three commands for each schema.
Grant replication access to this user:
Create publication that you’ll be using for creating the MIRROR (replication) in future.
Set wal_sender_timeout
to 0 for peerdb_user
The PeerDB user must not be restricted by RLS policies, as it can lead to missing data. You can disable RLS policies for the user by running the below command:
Sometimes to connect to your Postgres database you may need PeerDB to use an SSH tunnel.
This is typically used when your database is not publicly accessible and you need to connect to it a jump server in your VPC.
This is done by creating an SSH tunnel to your jump server and then connecting to the database through the tunnel. All of this is handled by PeerDB natively.
Generate a key-pair
Generate a key-pair using the following command:
This will generate a private key (peerdb_key.pem
) and a public key (peerdb_key.pub
).
Add public key to your jump server
Add the public key to your jump server. This can be done by adding the public key to the ~/.ssh/authorized_keys
file on the jump server.
Add private key to the connection
When creating a Postgres peer you can specify the option to use an SSH tunnel. There you will be able to provide the private key you generated in the first step along with the jump server details.
If you are using PeerDB Cloud, please follow the below steps to add peerdb ips to your network.
Add PeerDB IPs to Firewall
Through the PeerDB UI, create the Flexible Postgres Peer using the peerdb_user
that you created in the previous step.
Choose PostgreSQL Peer
Peer Creation and Validation
Created Peer