There's no comment on the DB field explaining the reasoning, so it's definitely a bug.

The migration that added it made a mistake of usingtimestamp vstimestamptz.

000043_workspace_last_used.up.sql2:    ADD COLUMN last_used_at timestamp NOT NULL DEFAULT '0001-01-01 00:00:00+00:00';

(See conflict between default value and field type.)

We should probably lint this somehow and prevent addition oftimestamp columns unless//nolinted.

Originally posted by@mafredri in#9672 (comment)