-- One row per account, written by the nightly off-host backup job when an
-- object lands in the bucket. The admin console reads it to say, per account,
-- whether the newest off-host copy is as fresh as the schedule promises,
-- without the page ever talking to the bucket.
CREATE TABLE "offhost_backup_state" (
    "user_id" TEXT NOT NULL,
    -- Written on every account the run walks, success or not. A row's mere
    -- existence is what lets the console tell "no run has reached this
    -- account yet" from "a run reached it and nothing landed".
    "last_attempt_at" TIMESTAMP(3) NOT NULL,
    -- NULL until an object lands for this account.
    "last_success_at" TIMESTAMP(3),
    -- BIGINT, not INTEGER: a single object may occupy 8 MiB x 10 000 multipart
    -- parts, so the uploader permits 80 GB and a 32-bit column would refuse
    -- every account past 2.1 GB.
    "size_bytes" BIGINT,

    CONSTRAINT "offhost_backup_state_pkey" PRIMARY KEY ("user_id")
);

ALTER TABLE "offhost_backup_state"
    ADD CONSTRAINT "offhost_backup_state_user_id_fkey"
    FOREIGN KEY ("user_id") REFERENCES "users"("id")
    ON DELETE CASCADE ON UPDATE CASCADE;