Zero chance. For one, it's written in Go. Postgres is written in C and needs to be portable to a lot more architectures than Go currently supports. Secondly, t

Zero chance. For one, it's written in Go. Postgres is written in C and needs to be portable to a lot more architectures than Go currently supports. Secondly, this is one possible design. The Postgres team prefers tools like these to complement the core so that people have a choice between different solutions depending on their use case, network topologies, availability tolerances, etc. This just a helper tool that can control Postgres and ship logs around. A native Postgres solution could do it better.