I assume you have reported the issues / crashes to pgcopydb. Wasn't it easier to fix them rather than rewriting from scratch? I assume rewrite was heavily AI driven, and if so, probably AI could have fixed pgcopydb rather than rewriting.
After fighting crash after crash with pgcopydb v17 and v18 I decided to bite the bullet and write my own in Golang.
I picked Golang because most issues with pgcopydb were related to concurrency bugs and memory leaks. There is nothing in this tool that requires C, Golang is totally fine and comes with a good concurrency built-in and a garbage collector.
A few more notable improvements:
- I use binary format instead wal2json
- Optional control plane with web interface
- CDC replay runs concurrently (partition by fk)
I assume you have reported the issues / crashes to pgcopydb. Wasn't it easier to fix them rather than rewriting from scratch? I assume rewrite was heavily AI driven, and if so, probably AI could have fixed pgcopydb rather than rewriting.
Or am I missing something?
After fighting crash after crash with pgcopydb v17 and v18 I decided to bite the bullet and write my own in Golang.
I picked Golang because most issues with pgcopydb were related to concurrency bugs and memory leaks. There is nothing in this tool that requires C, Golang is totally fine and comes with a good concurrency built-in and a garbage collector.
A few more notable improvements:
- I use binary format instead wal2json - Optional control plane with web interface - CDC replay runs concurrently (partition by fk)