UP20051 PostgreSQL Replication is Disabled

Possible Causes

Upsolver cannot create an ingestion job from the given PostgreSQL database because the WAL is disabled or configured using a non-supported mode.

Upsolver uses the WAL (Write Ahead Log) to read Change Data Capture changes from the database. This enables Upsolver to replicate the stream of changes that were applied to the database so they can be re-applied on a replica.

Possible Solutions

To solve this issue, change the WAL_LEVEL setting to either logical (preferred) or replicate.

Setting the WAL_LEVEL

Self-Hosted PostgreSQL

Run the following command from a user with administrator permissions:

ALTER SYSTEM SET WAL_LEVEL = logical;

If your database doesn't have a user with administrator permissions, you'll need to locate postgresql.conf. In most self-hosted PostgreSQL databases, the configuration file will be placed in /etc/postgresql/*/main/postgresql.conf.

1. Open the config file in an editor of your choice.

2. Check if a configuration value for WAL_LEVEL exists.

   1. If the value exists, update its value to the new value.

   2. If the value doesn't exist, add a new row at the end of the file as WAL_LEVEL = logical.

Restart the database so all changes take effect.

AWS RDS for PostgreSQL

1. Open the RDS Service in the Amazon Web Services Console.

2. Navigate to Databases.

3. Find the database that you want to modify and click on its Database Identifier.

4. Navigate to the Configuration tab.

5. Click on the value of DB Instance Parameter Group.

6. In the Filter parameters input, type rds.logical_replication.

7. Click on the checkbox before the name of the parameter rds.logical_replication in the table and click Edit Parameters.

8. Change the value to 1.

If the message "Error saving: Cannot modify a default parameter group." appears, please follow the guide to create an option group or copy an option group, and then modify the cluster to use the newly created DB parameter group, and retry steps 1 to 8.

After modifying the option group, you will need to restart your PostgreSQL instance by navigating to the RDS instance. Follow steps 1 to 3, click on the Actions button, and then click Reboot.