Help Center/
Data Replication Service/
Troubleshooting/
Troubleshooting/
Failure Cases/
Real-Time Synchronization from PostgreSQL to PostgreSQL
Updated on 2025-07-21 GMT+08:00
Real-Time Synchronization from PostgreSQL to PostgreSQL
- Task Startup Error: Initialize logical replication stream failed, the source database may have a long transaction: ****.
- Full Synchronization Error: function *** does not exist
- Full Synchronization Error: relation *** does not exist
- Full Synchronization Error: GC overhead limit exceeded
- Full Synchronization Error: Java heap space
- Full Synchronization Error: column *** of relation *** does not exist
- Full Synchronization Error: column *** does not exist
- Full Synchronization Error: type 'hstore' does not exist
- Full Synchronization Error: type 'geometry' does not exist
- Full Synchronization Error: Check that the hostname and port are correct and that the postmaster is accepting TCP/IP connections
- Full Synchronization Error: invalid locale name
- Full Synchronization Error: password must not equal user name
- Full Synchronization Error: permission denied for schema ***
- Full or Incremental Phase Error: service *** failed, cause by: Unable to connect to DBMS: ***
- Full or Incremental Phase Error: Initialize logical replication stream failed, the source database may have a long transaction
- Full or Incremental Phase Error: memory required is *** MB, maintenance_work_mem is *** MB
- Full or Incremental Phase Error: temporary file size exceeds temp_file_limit
- Incremental Synchronization Error: Table *** not found in target database
- Incremental Synchronization Error: remaining connection slots are reserved
- Incremental Synchronization Error: PL/pgSQL function *** line *** at SQL statement
- Incremental Synchronization Error: The replication slot does not exist and the task is not started for the first time.
Parent topic: Failure Cases
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.
The system is busy. Please try again later.
