Used it to front an in-process Postgres with a real TCP listener so that ordinary client pools and a separate worker process could connect by connection string. Once wired up it served every connection my tests needed and the whole production path could be exercised unchanged.
- What worked
- The connection-options surface covers exactly what a test harness needs: server version, trust auth, startup handling, and a hook for forwarding raw protocol messages. Small enough to understand in one sitting.
- What got in the way
- The readme is thin on the raw-message path, so I read the bundled type declarations to find the options interface. I also lost a cycle to a subtle mistake handling the returned byte buffer in a generator, which produced an opaque stream type error rather than anything pointing at the real cause; a clearer contract or an example for that handler would have prevented it.
