In 2038 we are all going to die

[alexgleason]

Consider this error message:

PostgresError: value "1705215483996" is out of range for type integer
  at Connection.#preparedQuery(/x/postgres@v0.17.0/connection/connection.ts:879:19)
  at eventLoopTick(ext:core/01_core.js:168:7)
  at Connection.query(/x/postgres@v0.17.0/connection/connection.ts:951:16)
  at PoolClient.#executeQuery(/x/postgres@v0.17.0/client.ts:245:12)
  at PoolClient.queryObject(/x/postgres@v0.17.0/client.ts:433:12)
  at PostgreSQLDriverDatabaseConnection.executeQuery(/x/kysely_deno_postgres@v0.4.0/src/PostgreSQLDriverDatabaseConnection.ts:14:12)
  at PostgreSQLDriverDatabaseConnection.connection.executeQuery(/home/ditto/.cache/deno/npm/registry.npmjs.org/kysely/0.27.3/dist/esm/driver/runtime-driver.js:90:24)
  at <anonymous>(/home/ditto/.cache/deno/npm/registry.npmjs.org/kysely/0.27.3/dist/esm/query-executor/query-executor-base.js:35:28)
  at DefaultConnectionProvider.provideConnection(/home/ditto/.cache/deno/npm/registry.npmjs.org/kysely/0.27.3/dist/esm/driver/default-connection-provider.js:10:20)
  at DefaultQueryExecutor.executeQuery(/home/ditto/.cache/deno/npm/registry.npmjs.org/kysely/0.27.3/dist/esm/query-executor/query-executor-base.js:34:16)

This is a Nostr event that somebody accidentally published with the created_at in milliseconds instead of seconds.

But it got me thinking. In just 14 years we are going to hit the integer max value with our timestamps: https://en.wikipedia.org/wiki/2,147,483,647

Then everything is going to explode.

[mterenzio]

2038 used to seem so far away . . .

…

On Wed, May 29, 2024 at 7:30 PM Alex Gleason ***@***.***> wrote: Consider this error message: PostgresError: value "1705215483996" is out of range for type integer at ***@***.***/connection/connection.ts:879:19) at eventLoopTick(ext:core/01_core.js:168:7) at ***@***.***/connection/connection.ts:951:16) at ***@***.***/client.ts:245:12) at ***@***.***/client.ts:433:12) at ***@***.***/src/PostgreSQLDriverDatabaseConnection.ts:14:12) at PostgreSQLDriverDatabaseConnection.connection.executeQuery(/home/ditto/.cache/deno/npm/registry.npmjs.org/kysely/0.27.3/dist/esm/driver/runtime-driver.js:90:24) at <anonymous>(/home/ditto/.cache/deno/npm/registry.npmjs.org/kysely/0.27.3/dist/esm/query-executor/query-executor-base.js:35:28) at DefaultConnectionProvider.provideConnection(/home/ditto/.cache/deno/npm/registry.npmjs.org/kysely/0.27.3/dist/esm/driver/default-connection-provider.js:10:20) at DefaultQueryExecutor.executeQuery(/home/ditto/.cache/deno/npm/registry.npmjs.org/kysely/0.27.3/dist/esm/query-executor/query-executor-base.js:34:16) This is a Nostr event that somebody accidentally published with the created_at in milliseconds instead of seconds. But it got me thinking. In just 14 years we are going to hit the integer max value with our timestamps: https://en.wikipedia.org/wiki/2,147,483,647 Then everything is going to explode. — Reply to this email directly, view it on GitHub <#1269>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAAAWDSNII566I6ID5IR4PTZEZQJPAVCNFSM6AAAAABIP3KA4GVHI2DSMVQWIX3LMV43ERDJONRXK43TNFXW4OZWG42DSNBUHA> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[mikedilger]

I've been using 64 bits for unix timestamps this whole time. I'm going to live for a very very long time indeed.