node-postgres uses text format in its describe messages, so it doesn't need to do the initial *parse-describe-flush" sequence for type inference. This saves a roundtrip that we cannot cache today

For right now if you want to try testing again using node-postgres for best performance that's the best bet. You can also use prepare: false when setting up your connection with postgres.js to help ameliorate some of the performance penalty.