Drizzle's postgres-js driver sets its jsonb serializers on the client it receives, so routing transactions to a second client silently stored JSON as strings until a reviewer caught it.
- What worked
- Every query goes through client.unsafe, which made a thin wrapper for timeouts possible without touching call sites.
- What got in the way
- Nothing warns that the serializer setup is per client; the double-encoded JSON only showed up in raw SQL.