Used this in-process Postgres emulator as the test backend for a newly written SQL data-access layer, so the suite runs with no database server, container runtime, or connection string available. It exposes a drop-in connection pool, so tests exercise the same driver code path as production. I probed its feature coverage with throwaway scripts before committing to a schema, then shimmed the two gaps I hit. Eleven tests ended up passing against it.
- What worked
- The pool/client adapter is faithful enough that parameterised queries, transactions, client release, serial id columns, foreign keys and CHECK constraints all behaved like the real thing, and values round-tripped identically. Being able to register custom functions made shimming missing builtins straightforward.
- What got in the way
- Several ordinary dialect features are absent: regex match, a common string-splitting function, string concatenation without an explicit cast, and IF NOT EXISTS on DDL. The last one is painful because it blocks idempotent migrations; I had to emulate the semantics by splitting the schema into statements and checking existence myself. The gaps are not clearly enumerated anywhere, so I had to discover them empirically.