2.0 -> 2.1 errors

[neill12]

Just tried to update to 2.1, normally my procedure is to redeploy my TeslaMate stack, Grafana, Teslamate are all on 'latest' branch and Mosquitto is on :2 and Postgres is on :17

Getting the following after upgrading:

2025-07-22 19:49:00.428 [info] == Running 20250613133700 TeslaMate.Repo.Migrations.AddAndCalculateElevationChanges.up/0 forward

2025-07-22 19:49:00.430 [info] alter table drives

2025-07-22 19:49:00.432 [info] execute "WITH elevation_changes AS (\n  SELECT\n    drive_id,\n    SUM(CASE WHEN elevation_diff > 0 THEN elevation_diff ELSE 0 END) as ascent,\n    SUM(CASE WHEN elevation_diff < 0 THEN ABS(elevation_diff) ELSE 0 END) as descent\n  FROM (\n    SELECT\n      drive_id,\n      elevation - LAG(elevation) OVER (PARTITION BY drive_id ORDER BY date) as elevation_diff\n    FROM positions\n    WHERE elevation IS NOT NULL\n  ) as changes\n  GROUP BY drive_id\n)\nUPDATE drives d\nSET\n  ascent = ec.ascent,\n  descent = ec.descent\nFROM elevation_changes ec\nWHERE d.id = ec.drive_id;\n"

** (Postgrex.Error) ERROR 22003 (numeric_value_out_of_range) smallint out of range

    (ecto_sql 3.12.1) lib/ecto/adapters/sql.ex:1096: Ecto.Adapters.SQL.raise_sql_call_error/1

    (elixir 1.17.3) lib/enum.ex:1703: Enum."-map/2-lists^map/1-1-"/2

    (ecto_sql 3.12.1) lib/ecto/adapters/sql.ex:1203: Ecto.Adapters.SQL.execute_ddl/4

    (ecto_sql 3.12.1) lib/ecto/migration/runner.ex:348: Ecto.Migration.Runner.log_and_execute_ddl/3

    (elixir 1.17.3) lib/enum.ex:1703: Enum."-map/2-lists^map/1-1-"/2

    (elixir 1.17.3) lib/enum.ex:1703: Enum."-map/2-lists^map/1-1-"/2

    (ecto_sql 3.12.1) lib/ecto/migration/runner.ex:311: Ecto.Migration.Runner.perform_operation/3

This repeats forever

I've reverted to previous v2.0 snapshot

thanks ain advance

[brianmay]

Are you sure about the postgres version?

This does look very much similar to the errors people reported when their postgres was too old, e.g. #4841

[neill12]

Hi, yep v17

PG_MAJOR | 17
PG_VERSION | 17.4-1.pgdg120+2

[neill12]

I see the minimum supported Postgress version is 17.3, the installation this is affecting is 17.4

[SorenLan]

Exactly the same issue here. Yes, the database is postgres 17:

psql (17.5 (Debian 17.5-1.pgdg120+1))

[JakobLichterfeld]

--> #4876