duplicate sql queries on production build (Prisma adapter thing?)

[swport]

Environment

System:
    OS: Linux 5.19 Ubuntu 22.04.1 LTS 22.04.1 LTS (Jammy Jellyfish)
    CPU: (8) x64 Intel(R) Core(TM) i5-8250U CPU @ 1.60GHz
    Memory: 3.46 GB / 7.68 GB
    Container: Yes
    Shell: 5.8.1
  Binaries:
    Node: 16.17.0
    Yarn: 1.22.19
    npm: 8.15.0 
  Browsers:
    Chromium: 111.0.5563.110
    Firefox: 111.0.

Reproduction URL

https://github.com/t3-oss/create-t3-app

Describe the issue

Seeing duplicating queries being logged (and ran, probably) into the console after running a production build.

First time login via google provider:

prisma:query SELECT `twitter-clone`.`Account`.`id`, `twitter-clone`.`Account`.`userId` FROM `twitter-clone`.`Account` WHERE ((`twitter-clone`.`Account`.`provider` = ? AND `twitter-clone`.`Account`.`providerAccountId` = ?) AND 1=1) LIMIT ? OFFSET ?
prisma:query SELECT `twitter-clone`.`Account`.`id`, `twitter-clone`.`Account`.`userId` FROM `twitter-clone`.`Account` WHERE ((`twitter-clone`.`Account`.`provider` = ? AND `twitter-clone`.`Account`.`providerAccountId` = ?) AND 1=1) LIMIT ? OFFSET ?
prisma:query SELECT `twitter-clone`.`User`.`id`, `twitter-clone`.`User`.`username`, `twitter-clone`.`User`.`name`, `twitter-clone`.`User`.`email`, `twitter-clone`.`User`.`emailVerified`, `twitter-clone`.`User`.`image`, `twitter-clone`.`User`.`followingCount`, `twitter-clone`.`User`.`followersCount`, `twitter-clone`.`User`.`pinnedPostId` FROM `twitter-clone`.`User` WHERE (`twitter-clone`.`User`.`email` = ? AND 1=1) LIMIT ? OFFSET ?
prisma:query BEGIN
prisma:query INSERT INTO `twitter-clone`.`User` (`id`,`username`,`name`,`email`,`emailVerified`,`image`,`followingCount`,`followersCount`) VALUES (?,?,?,?,?,?,?,?)
prisma:query SELECT `twitter-clone`.`User`.`id`, `twitter-clone`.`User`.`username`, `twitter-clone`.`User`.`name`, `twitter-clone`.`User`.`email`, `twitter-clone`.`User`.`emailVerified`, `twitter-clone`.`User`.`image`, `twitter-clone`.`User`.`followingCount`, `twitter-clone`.`User`.`followersCount`, `twitter-clone`.`User`.`pinnedPostId` FROM `twitter-clone`.`User` WHERE `twitter-clone`.`User`.`id` = ? LIMIT ? OFFSET ?
prisma:query COMMIT
prisma:query BEGIN
prisma:query INSERT INTO `twitter-clone`.`Account` (`id`,`userId`,`type`,`provider`,`providerAccountId`,`access_token`,`expires_at`,`token_type`,`scope`,`id_token`) VALUES (?,?,?,?,?,?,?,?,?,?)
prisma:query SELECT `twitter-clone`.`Account`.`id`, `twitter-clone`.`Account`.`userId`, `twitter-clone`.`Account`.`type`, `twitter-clone`.`Account`.`provider`, `twitter-clone`.`Account`.`providerAccountId`, `twitter-clone`.`Account`.`refresh_token`, `twitter-clone`.`Account`.`access_token`, `twitter-clone`.`Account`.`expires_at`, `twitter-clone`.`Account`.`token_type`, `twitter-clone`.`Account`.`scope`, `twitter-clone`.`Account`.`id_token`, `twitter-clone`.`Account`.`session_state` FROM `twitter-clone`.`Account` WHERE `twitter-clone`.`Account`.`id` = ? LIMIT ? OFFSET ?

Second time login via google provider

prisma:query SELECT `twitter-clone`.`Account`.`id`, `twitter-clone`.`Account`.`userId` FROM `twitter-clone`.`Account` WHERE ((`twitter-clone`.`Account`.`provider` = ? AND `twitter-clone`.`Account`.`providerAccountId` = ?) AND 1=1) LIMIT ? OFFSET ?
prisma:query SELECT `twitter-clone`.`User`.`id`, `twitter-clone`.`User`.`username`, `twitter-clone`.`User`.`name`, `twitter-clone`.`User`.`email`, `twitter-clone`.`User`.`emailVerified`, `twitter-clone`.`User`.`image`, `twitter-clone`.`User`.`followingCount`, `twitter-clone`.`User`.`followersCount`, `twitter-clone`.`User`.`pinnedPostId` FROM `twitter-clone`.`User` WHERE `twitter-clone`.`User`.`id` IN (?)
prisma:query SELECT `twitter-clone`.`Account`.`id`, `twitter-clone`.`Account`.`userId` FROM `twitter-clone`.`Account` WHERE ((`twitter-clone`.`Account`.`provider` = ? AND `twitter-clone`.`Account`.`providerAccountId` = ?) AND 1=1) LIMIT ? OFFSET ?
prisma:query SELECT `twitter-clone`.`User`.`id`, `twitter-clone`.`User`.`username`, `twitter-clone`.`User`.`name`, `twitter-clone`.`User`.`email`, `twitter-clone`.`User`.`emailVerified`, `twitter-clone`.`User`.`image`, `twitter-clone`.`User`.`followingCount`, `twitter-clone`.`User`.`followersCount`, `twitter-clone`.`User`.`pinnedPostId` FROM `twitter-clone`.`User` WHERE `twitter-clone`.`User`.`id` IN (?)

How to reproduce

1. Integrate any third party auth provider
2. Enable query to PrismaClient client instance in src/server/db.ts, inside production array.
3. Run the following commands

yarn run build
yarn run dev

4. Attempt social login and check console.

Thus far I've only integrated Google login in next auth config. Built the app with query param in PrismaClient. Ran it and saw duplicating sql queries in console.

Could potentially be Prisma adapter issue. Not sure.

Expected behavior

It shouldn't make duplicate requests