1 Answer
- Newest
- Most votes
- Most comments
1
Hi David,
This error log is a known issue and will be patched likely in our next Aurora PostgreSQL release.
In the interim, in order to mitigate the issue, disable the logical WAL cache feature by setting the cluster parameter 'rds.logical_wal_cache' to 0 and restarting your writer instance. Please rest assured that disabling this will not result in any loss of data from existing logical replication publications.
I hope that helps :)
Relevant content
- Accepted Answerasked 3 years ago
- asked 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 4 years ago
- AWS OFFICIALUpdated 10 months ago
- AWS OFFICIALUpdated a year ago
Thanks a lot Brandon! Very helpful ! :)
Hi Brandon, I wonder which versions are affected?
Best regards, Alex