Writing a Postgres Foreign Data Wrapper for Clickhouse in Go

I wonder if you&#x27;ve benchmarked your Go implementation against the Percona Lab&#x27;s FDW for Clickhouse? <a href="https:&#x2F;&#x2F;github.com&#x2F;Percona-Lab&#x2F;clickhousedb_fdw" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;Percona-Lab&#x2F;clickhousedb_fdw</a>

I sometimes fondly remember my time as an office hero, using MSAccess to attach to just about any data source imaginable, copy to a temptable and run whatever cleaning was required before loading into the server database.<p>Good times; almost 25 years ago now. Sometimes I wonder if we&#x27;re stuck.

This is really cool. I had not heard of Foreign Data Wrappers for Postgres before! Are these used in production commonly or more of a toy thing?

I have done something similar. For a software, which take shared libraries - usually written in C - as plugins, I wrote such a plugin in Go. This was a very good experience. It took only little work to set up the C compatible Go functions realizing the API, but the rest I could implement in Go which made the life so nice. I also ended up calling back into some of the applications APIs from Go, that worked seamlessly.<p>Go has good facilities interfacing with C, the only attention you need to pay is properly handling C pointers (manual memory management) vs. Go pointers (automatically managed via the GC). But with very little care this is not a big issue. The Go part of the code is however much nicer than if you had to implement the functionality in C. (Yes, I do think that Go is a great C replacement)

So, naive question, and I know the concept of a ‘database’ is a bit different between MySQL and Postgres, does Postgres require a FDW to communicate between multiple databases on the same server?