Hey folks, I'm running into an issue with Prisma raw queries, that are failing under high load. I cannot recreate it under normal load. The same query eventually succeeds after several attempts. I could understand if the bind parameter actually had an invalid value, but that wouldn't explain why it eventually works. It either consistently works, or doesn't. Bind parameter 26 is either a Prisma.Decimal or null. I'm using queryRawUnsafe `{"clientVersion":"4.2.0","code":"P2010","level":"error","message":"uncaught gql exception Raw query failed. Code:

22P03

. Message: `db error: ERROR: incorrect binary data format in bind parameter 26`","meta":{"code":"22P03","message":"db error: ERROR: incorrect binary data format in bind parameter 26"},"stack":"Error: Raw query failed. Code:

22P03

. Message: `db error: ERROR: incorrect binary data format in bind parameter 26`\n at RequestHandler.handleRequestError (/home/site/wwwroot/node_modules/@prisma/client/runtime/index.js2883113)\n at RequestHandler.request (/home/site/wwwroot/node_modules/@prisma/client/runtime/index.js2881312)\n at async Proxy._request (/home/site/wwwroot/node_modules/@prisma/client/runtime/index.js2973816)\n at async DeferralService.upsertDeferralChangeLog (/home/site/wwwroot/dist/src/deferral/deferral.service.js37538)\n at async target (/home/site/wwwroot/node_modules/@nestjs/core/helpers/external-context-creator.js7728)\n at async Object.upsertDeferralChangeLog (/home/site/wwwroot/node_modules/@nestjs/core/helpers/external-proxy.js924)","timestamp":"2022-08-23T215556.454Z"}`

Hey 👋 Welcome to our Slack community! 🙌 Could you please create a Bug Report for this and provide us with a minimal sample reproduction so that we could debug this?