`createdAt @default(now())` and `updatedAt @updatedAt` get different times on row creation

Bug description

I have standard table like this:

model User {
  id                     String              @id @default(cuid())
  createdAt              DateTime            @default(now())
  updatedAt              DateTime            @updatedAt
}

I always assumed that after a prisma.user.create({}), the createdAt and updatedAt would be the same dates, matching to the millisecond. I’m seeing that’s not the case and updatedAt many times has a few extra millisecond(s).

How to reproduce

1. Create the table above
2. Add many rows and log the query result
3. You’ll see what I describe eventually

Expected behavior

On creation, createdAt and updatedAt are always identical. I suppose if @updatedAt kind of columns would also default to CURRENT_TIMESTAMP like the default(now()) do, the problem would be resolved

Prisma information

The schema above is enough

Environment & setup

• OS: Ubuntu 20
• Database: PostgreSQL
• Node.js version: v14.17.0

Prisma Version

prisma                  : 3.6.0
@prisma/client          : 3.6.0
Current platform        : debian-openssl-1.1.x
Query Engine (Node-API) : libquery-engine dc520b92b1ebb2d28dc3161f9f82e875bd35d727 (at node_modules/@prisma/engines/libquery_engine-debian-openssl-1.1.x.so.node)
Migration Engine        : migration-engine-cli dc520b92b1ebb2d28dc3161f9f82e875bd35d727 (at node_modules/@prisma/engines/migration-engine-debian-openssl-1.1.x)
Introspection Engine    : introspection-core dc520b92b1ebb2d28dc3161f9f82e875bd35d727 (at node_modules/@prisma/engines/introspection-engine-debian-openssl-1.1.x)
Format Binary           : prisma-fmt dc520b92b1ebb2d28dc3161f9f82e875bd35d727 (at node_modules/@prisma/engines/prisma-fmt-debian-openssl-1.1.x)
Default Engines Hash    : dc520b92b1ebb2d28dc3161f9f82e875bd35d727
Studio                  : 0.440.0
Preview Features        : filterJson