Obtaining the Delayed Replay Status of WAL Logs
Function
This API is used to obtain the delayed WAL replay status of a read replica.
- Before calling an API, you need to understand the API in Authentication.
Constraints
- To use this function, contact customer service to obtain required permissions.
- This function is only available to read replicas of RDS for PostgreSQL 12 and later versions.
URI
- Parameter description
Table 1 Parameters Parameter
Mandatory
Description
project_id
Yes
Project ID of a tenant in a region.
For details about how to obtain the project ID, see Obtaining a Project ID.
instance_id
Yes
Instance ID.
Request
Response
- Normal response
Table 2 Parameters Parameter
Type
Description
cur_delay_time_mills
int
Configured delay, in ms.
The replication delay is controlled by the recovery_min_apply_delay parameter. You can modify this parameter to change the delay for replaying WAL logs. For details about how to modify this parameter, see Modifying Parameters of a Specified Instance.
delay_time_value_range
String
Value range for the delay.
real_delay_time_mills
int
Actual delay, in ms.
cur_log_replay_paused
boolean
Current log replay status.
- true: The replay is paused.
- false: The replay is normal.
latest_receive_log
String
Latest received log position.
latest_replay_log
String
Latest replayed log position.
- Example normal response
{ "cur_delay_time_mills" : 0, "delay_time_value_range" : "0-2147483647", "real_delay_time_mills" : 0, "cur_log_replay_paused" : true, "latest_receive_log" : "0/8000060", "latest_replay_log" : "0/8000060" }
- Abnormal response
For details, see Abnormal Request Results.
Status Code
- Normal
- Abnormal
For details, see Status Codes.
Error Code
For details, see Error Codes.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot