Postgres having error in logs after update to latest immich_server version (immich is running)
Immich is running and accessible via web. Yet I found this error in the postgres container of immich after updating
Was curious if theres a fix
PostgreSQL Database directory appears to contain a database; Skipping initialization
Was curious if theres a fix
PostgreSQL Database directory appears to contain a database; Skipping initialization
2023-06-20 15:20:14.478 UTC [1] LOG: starting PostgreSQL 14.8 on x86_64-pc-linux-musl, compiled by gcc (Alpine 12.2.1_git20220924-r10) 12.2.1 20220924, 64-bit
2023-06-20 15:20:14.479 UTC [1] LOG: listening on IPv4 address "0.0.0.0", port 5432
2023-06-20 15:20:14.479 UTC [1] LOG: listening on IPv6 address "::", port 5432
2023-06-20 15:20:14.493 UTC [1] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2023-06-20 15:20:14.516 UTC [22] LOG: database system was shut down at 2023-06-20 15:19:47 UTC
2023-06-20 15:20:14.576 UTC [1] LOG: database system is ready to accept connections
2023-06-24 22:20:01.423 UTC [26] LOG: using stale statistics instead of current ones because stats collector is not responding
2023-07-17 06:23:22.917 UTC [26] LOG: using stale statistics instead of current ones because stats collector is not responding
2023-07-23 17:22:29.847 UTC [96581] ERROR: column "isReadOnly" of relation "assets" already exists
2023-07-23 17:22:29.847 UTC [96581] STATEMENT: ALTER TABLE "assets" ADD "isReadOnly" boolean NOT NULL DEFAULT false2023-06-20 15:20:14.478 UTC [1] LOG: starting PostgreSQL 14.8 on x86_64-pc-linux-musl, compiled by gcc (Alpine 12.2.1_git20220924-r10) 12.2.1 20220924, 64-bit
2023-06-20 15:20:14.479 UTC [1] LOG: listening on IPv4 address "0.0.0.0", port 5432
2023-06-20 15:20:14.479 UTC [1] LOG: listening on IPv6 address "::", port 5432
2023-06-20 15:20:14.493 UTC [1] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2023-06-20 15:20:14.516 UTC [22] LOG: database system was shut down at 2023-06-20 15:19:47 UTC
2023-06-20 15:20:14.576 UTC [1] LOG: database system is ready to accept connections
2023-06-24 22:20:01.423 UTC [26] LOG: using stale statistics instead of current ones because stats collector is not responding
2023-07-17 06:23:22.917 UTC [26] LOG: using stale statistics instead of current ones because stats collector is not responding
2023-07-23 17:22:29.847 UTC [96581] ERROR: column "isReadOnly" of relation "assets" already exists
2023-07-23 17:22:29.847 UTC [96581] STATEMENT: ALTER TABLE "assets" ADD "isReadOnly" boolean NOT NULL DEFAULT false