Before enabling read/write separation, confirm a read-only node is created. If you encounter errors with read/write separation, troubleshoot using the following suggestions:

Confirm that the PostgreSQL instance is in the Running state.

Confirm that you've created a read-only node for the instance and the instance is in the Running status.

If errors with read/write separation persist after troubleshooting, you can submit a ticket to contact technical support.

What happens when read/write separation is enabled?

After read/write splitting is enabled, the PostgreSQL instance can be accessed by the read/write splitting address, and requests can be automatically forwarded to the read-only nodes. If a transaction contains both read and write requests, they are sent to the primary node for execution. For more information, refer to Enabling or disabling read/write separation.

What is global read-only?

Once global read-only is enabled, you can set the PostgreSQL instance to read-only, so that write requests will not be forwarded to the instance.

Does enabling global read-only override account privileges?

After global read-only is enabled, only read permission is available.

Last updated: 2025.11.17 16:15:12

Public security network record in Beijing: No. 11010802032137