You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
After upgrading to v5 sometimes it fails to scan timestamps from database, randomly, most of the time it does it but if it is running long enough it starts to fail.
To Reproduce
Unable in non-production environment (so far)
Expected behavior
In v4 timestamps were scanning perfectly fine.
Actual behavior
In v5, after some time of process/server running it starts to fail to scan timestamps.
Version
Go: go version go1.22.4 linux/amd64
PostgreSQL: PostgreSQL 16.6 (Ubuntu 16.6-0ubuntu0.24.04.1) on x86_64-pc-linux-gnu, compiled by gcc (Ubuntu 13.2.0-23ubuntu4) 13.2.0, 64-bit
pgx: github.com/jackc/pgx/v5 v5.7.2
Additional context
It seems to only fail if destination/field is nullable, never seen it fail to scan *time.Time
The text was updated successfully, but these errors were encountered:
Describe the bug
After upgrading to v5 sometimes it fails to scan timestamps from database, randomly, most of the time it does it but if it is running long enough it starts to fail.
To Reproduce
Unable in non-production environment (so far)
Expected behavior
In v4 timestamps were scanning perfectly fine.
Actual behavior
In v5, after some time of process/server running it starts to fail to scan timestamps.
Version
go version go1.22.4 linux/amd64
PostgreSQL 16.6 (Ubuntu 16.6-0ubuntu0.24.04.1) on x86_64-pc-linux-gnu, compiled by gcc (Ubuntu 13.2.0-23ubuntu4) 13.2.0, 64-bit
github.com/jackc/pgx/v5 v5.7.2
Additional context
It seems to only fail if destination/field is nullable, never seen it fail to scan *time.Time
The text was updated successfully, but these errors were encountered: