immich-app/immich
1
0
Fork 0
mirror of https://github.com/immich-app/immich.git synced 2026-02-05 00:30:57 +03:00
Code Issues 11 Packages Projects Releases 10 Wiki Activity

[BUG] After update to 1.78 it stopped working! Database issue #1334

New Issue
Closed
opened 2026-02-05 01:17:49 +03:00 by OVERLORD · 4 comments
OVERLORD commented 2026-02-05 01:17:49 +03:00
Owner
Copy Link

Originally created by @Majestic7979 on GitHub (Sep 17, 2023).

The bug

Now my docker log for the db container shows this:

2023-09-17 00:14:54.144 UTC [30] FATAL: the database system is starting up
2023-09-17 00:14:54.883 UTC [1] LOG: database system is ready to accept connections
2023-09-17 00:16:05.850 UTC [40] ERROR: could not obtain lock on row in relation "ir_cron"
2023-09-17 00:16:05.850 UTC [40] STATEMENT:
SELECT id
FROM "ir_cron"
WHERE id IN (5)
FOR NO KEY UPDATE NOWAIT

2023-09-17 00:19:16.764 UTC [41] ERROR: could not obtain lock on row in relation "ir_cron"
2023-09-17 00:19:16.764 UTC [41] STATEMENT:
SELECT id
FROM "ir_cron"
WHERE id IN (5)
FOR NO KEY UPDATE NOWAIT

2023-09-17 00:19:54.192 UTC [27] LOG: checkpoint starting: time
2023-09-17 00:20:00.753 UTC [27] LOG: checkpoint complete: wrote 4 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.202 s, sync=2.631 s, total=6.561 s; sync files=5, longest=1.124 s, average=0.527 s; distance=9 kB, estimate=9 kB

So Immich does not start. 502 nginx error. HELP!!!

The OS that Immich Server is running on

Debian 12

Version of Immich Server

1.78

Version of Immich Mobile App

NA

Platform with the issue

  • Server
  • Web
  • Mobile

Your docker-compose.yml content

docker create --name=immich --restart=unless-stopped --gpus=all -p 5456:8080 -e PUID=1000 -e PGID=1000 -e TZ=Europe/London -e DB_HOSTNAME=10.0.0.xxx -e DB_USERNAME=xxxx -e DB_PASSWORD="xxxxxxxxxxxxxxxxx" -e DB_DATABASE_NAME=immich -e REDIS_HOSTNAME=10.0.0.xxx -e DISABLE_MACHINE_LEARNING=false -e DISABLE_TYPESENSE=false -e DB_PORT=5432 -e REDIS_PORT=6379  -v /home/user/docker/immich/config:/config -v /home/user/files/originals:/photos -v /home/user/docker/immich/machine-learning:/config/machine-learning ghcr.io/imagegenius/immich:latest && docker start immich

Your .env content

na

Reproduction steps

na

Additional information

No response

Originally created by @Majestic7979 on GitHub (Sep 17, 2023). ### The bug Now my docker log for the db container shows this: 2023-09-17 00:14:54.144 UTC [30] FATAL: the database system is starting up 2023-09-17 00:14:54.883 UTC [1] LOG: database system is ready to accept connections 2023-09-17 00:16:05.850 UTC [40] ERROR: could not obtain lock on row in relation "ir_cron" 2023-09-17 00:16:05.850 UTC [40] STATEMENT: SELECT id FROM "ir_cron" WHERE id IN (5) FOR NO KEY UPDATE NOWAIT 2023-09-17 00:19:16.764 UTC [41] ERROR: could not obtain lock on row in relation "ir_cron" 2023-09-17 00:19:16.764 UTC [41] STATEMENT: SELECT id FROM "ir_cron" WHERE id IN (5) FOR NO KEY UPDATE NOWAIT 2023-09-17 00:19:54.192 UTC [27] LOG: checkpoint starting: time 2023-09-17 00:20:00.753 UTC [27] LOG: checkpoint complete: wrote 4 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.202 s, sync=2.631 s, total=6.561 s; sync files=5, longest=1.124 s, average=0.527 s; distance=9 kB, estimate=9 kB So Immich does not start. 502 nginx error. HELP!!! ### The OS that Immich Server is running on Debian 12 ### Version of Immich Server 1.78 ### Version of Immich Mobile App NA ### Platform with the issue - [X] Server - [ ] Web - [ ] Mobile ### Your docker-compose.yml content ```YAML docker create --name=immich --restart=unless-stopped --gpus=all -p 5456:8080 -e PUID=1000 -e PGID=1000 -e TZ=Europe/London -e DB_HOSTNAME=10.0.0.xxx -e DB_USERNAME=xxxx -e DB_PASSWORD="xxxxxxxxxxxxxxxxx" -e DB_DATABASE_NAME=immich -e REDIS_HOSTNAME=10.0.0.xxx -e DISABLE_MACHINE_LEARNING=false -e DISABLE_TYPESENSE=false -e DB_PORT=5432 -e REDIS_PORT=6379 -v /home/user/docker/immich/config:/config -v /home/user/files/originals:/photos -v /home/user/docker/immich/machine-learning:/config/machine-learning ghcr.io/imagegenius/immich:latest && docker start immich ``` ### Your .env content ```Shell na ``` ### Reproduction steps ```bash na ``` ### Additional information _No response_
OVERLORD commented 2026-02-05 01:17:56 +03:00
Author
Owner
Copy Link

@Majestic7979 commented on GitHub (Sep 17, 2023):

	                    FROM "ir_cron"
	                    WHERE id IN (5)
	                    FOR NO KEY UPDATE NOWAIT
	                
2023-09-17 00:05:25.090 UTC [27] LOG:  checkpoint starting: time
2023-09-17 00:05:25.440 UTC [27] LOG:  checkpoint complete: wrote 3 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.201 s, sync=0.055 s, total=0.350 s; sync files=3, longest=0.038 s, average=0.019 s; distance=8 kB, estimate=15 kB
2023-09-17 00:08:48.389 UTC [49] ERROR:  could not obtain lock on row in relation "ir_cron"
2023-09-17 00:08:48.389 UTC [49] STATEMENT:  
	                    SELECT id
	                    FROM "ir_cron"
	                    WHERE id IN (5)
	                    FOR NO KEY UPDATE NOWAIT
	                
2023-09-17 00:10:25.540 UTC [27] LOG:  checkpoint starting: time
2023-09-17 00:10:25.850 UTC [27] LOG:  checkpoint complete: wrote 3 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.201 s, sync=0.034 s, total=0.310 s; sync files=3, longest=0.017 s, average=0.012 s; distance=8 kB, estimate=14 kB
2023-09-17 00:13:20.188 UTC [1] LOG:  received fast shutdown request
2023-09-17 00:13:20.231 UTC [1] LOG:  aborting any active transactions
2023-09-17 00:13:20.231 UTC [50] FATAL:  terminating connection due to administrator command
2023-09-17 00:13:20.231 UTC [49] FATAL:  terminating connection due to administrator command
2023-09-17 00:13:20.231 UTC [39] FATAL:  terminating connection due to administrator command
2023-09-17 00:13:20.233 UTC [512] FATAL:  terminating connection due to administrator command
2023-09-17 00:13:20.234 UTC [504] FATAL:  terminating connection due to administrator command
2023-09-17 00:13:20.234 UTC [464] FATAL:  terminating connection due to administrator command
2023-09-17 00:13:20.234 UTC [115] FATAL:  terminating connection due to administrator command
2023-09-17 00:13:20.234 UTC [265] FATAL:  terminating connection due to administrator command
2023-09-17 00:13:20.235 UTC [511] FATAL:  terminating connection due to administrator command
2023-09-17 00:13:20.240 UTC [34] FATAL:  terminating connection due to administrator command
2023-09-17 00:13:20.240 UTC [501] FATAL:  terminating connection due to administrator command
2023-09-17 00:13:20.240 UTC [75] FATAL:  terminating connection due to administrator command
2023-09-17 00:13:20.240 UTC [341] FATAL:  terminating connection due to administrator command
2023-09-17 00:13:20.242 UTC [1] LOG:  background worker "logical replication launcher" (PID 33) exited with exit code 1
2023-09-17 00:13:20.260 UTC [27] LOG:  shutting down
2023-09-17 00:13:20.287 UTC [27] LOG:  checkpoint starting: shutdown immediate
2023-09-17 00:13:20.352 UTC [27] LOG:  checkpoint complete: wrote 1 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.001 s, sync=0.015 s, total=0.092 s; sync files=1, longest=0.015 s, average=0.015 s; distance=0 kB, estimate=13 kB
2023-09-17 00:13:20.364 UTC [1] LOG:  database system is shut down
PostgreSQL Database directory appears to contain a database; Skipping initialization
2023-09-17 00:14:53.247 UTC [1] LOG:  starting PostgreSQL 15.4 (Debian 15.4-2.pgdg120+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 12.2.0-14) 12.2.0, 64-bit
2023-09-17 00:14:53.281 UTC [1] LOG:  listening on IPv4 address "0.0.0.0", port 5432
2023-09-17 00:14:53.281 UTC [1] LOG:  listening on IPv6 address "::", port 5432
2023-09-17 00:14:53.562 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2023-09-17 00:14:54.093 UTC [29] LOG:  database system was shut down at 2023-09-17 00:13:20 UTC
2023-09-17 00:14:54.144 UTC [30] FATAL:  the database system is starting up
2023-09-17 00:14:54.883 UTC [1] LOG:  database system is ready to accept connections
2023-09-17 00:16:05.850 UTC [40] ERROR:  could not obtain lock on row in relation "ir_cron"
2023-09-17 00:16:05.850 UTC [40] STATEMENT:  
	                    SELECT id
	                    FROM "ir_cron"
	                    WHERE id IN (5)
	                    FOR NO KEY UPDATE NOWAIT
	                
2023-09-17 00:19:16.764 UTC [41] ERROR:  could not obtain lock on row in relation "ir_cron"
2023-09-17 00:19:16.764 UTC [41] STATEMENT:  
	                    SELECT id
	                    FROM "ir_cron"
	                    WHERE id IN (5)
	                    FOR NO KEY UPDATE NOWAIT
	                
2023-09-17 00:19:54.192 UTC [27] LOG:  checkpoint starting: time
2023-09-17 00:20:00.753 UTC [27] LOG:  checkpoint complete: wrote 4 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.202 s, sync=2.631 s, total=6.561 s; sync files=5, longest=1.124 s, average=0.527 s; distance=9 kB, estimate=9 kB
2023-09-17 00:23:31.235 UTC [39] ERROR:  could not obtain lock on row in relation "ir_cron"
2023-09-17 00:23:31.235 UTC [39] STATEMENT:  
	                    SELECT id
	                    FROM "ir_cron"
	                    WHERE id IN (5)
	                    FOR NO KEY UPDATE NOWAIT
	                
2023-09-17 00:24:54.852 UTC [27] LOG:  checkpoint starting: time
2023-09-17 00:24:56.084 UTC [27] LOG:  checkpoint complete: wrote 12 buffers (0.1%); 0 WAL file(s) added, 0 removed, 0 recycled; write=1.103 s, sync=0.062 s, total=1.232 s; sync files=4, longest=0.037 s, average=0.016 s; distance=59 kB, estimate=59 kB
2023-09-17 00:28:48.507 UTC [40] ERROR:  could not obtain lock on row in relation "ir_cron"
2023-09-17 00:28:48.507 UTC [40] STATEMENT:  
	                    SELECT id
	                    FROM "ir_cron"
	                    WHERE id IN (5)
	                    FOR NO KEY UPDATE NOWAIT
	                
2023-09-17 00:29:54.180 UTC [27] LOG:  checkpoint starting: time
2023-09-17 00:29:54.547 UTC [27] LOG:  checkpoint complete: wrote 3 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.202 s, sync=0.091 s, total=0.367 s; sync files=3, longest=0.073 s, average=0.031 s; distance=10 kB, estimate=54 kB
2023-09-17 00:30:47.930 UTC [1] LOG:  received fast shutdown request
2023-09-17 00:30:48.003 UTC [1] LOG:  aborting any active transactions
2023-09-17 00:30:48.003 UTC [40] FATAL:  terminating connection due to administrator command
2023-09-17 00:30:48.004 UTC [41] FATAL:  terminating connection due to administrator command
2023-09-17 00:30:48.004 UTC [35] FATAL:  terminating connection due to administrator command
2023-09-17 00:30:48.004 UTC [39] FATAL:  terminating connection due to administrator command
2023-09-17 00:30:48.007 UTC [1] LOG:  background worker "logical replication launcher" (PID 33) exited with exit code 1
2023-09-17 00:30:48.010 UTC [27] LOG:  shutting down
2023-09-17 00:30:48.024 UTC [27] LOG:  checkpoint starting: shutdown immediate
2023-09-17 00:30:48.038 UTC [84] FATAL:  the database system is shutting down
2023-09-17 00:30:48.092 UTC [27] LOG:  checkpoint complete: wrote 0 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.001 s, sync=0.001 s, total=0.083 s; sync files=0, longest=0.000 s, average=0.000 s; distance=0 kB, estimate=48 kB
2023-09-17 00:30:48.096 UTC [1] LOG:  database system is shut down
PostgreSQL Database directory appears to contain a database; Skipping initialization
2023-09-17 00:30:48.660 UTC [1] LOG:  starting PostgreSQL 15.4 (Debian 15.4-2.pgdg120+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 12.2.0-14) 12.2.0, 64-bit
2023-09-17 00:30:48.660 UTC [1] LOG:  listening on IPv4 address "0.0.0.0", port 5432
2023-09-17 00:30:48.660 UTC [1] LOG:  listening on IPv6 address "::", port 5432
2023-09-17 00:30:48.671 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2023-09-17 00:30:48.726 UTC [29] LOG:  database system was shut down at 2023-09-17 00:30:48 UTC
2023-09-17 00:30:48.760 UTC [1] LOG:  database system is ready to accept connections

This is the docker logs for the database container.

@Majestic7979 commented on GitHub (Sep 17, 2023): ``` FROM "ir_cron" WHERE id IN (5) FOR NO KEY UPDATE NOWAIT 2023-09-17 00:05:25.090 UTC [27] LOG: checkpoint starting: time 2023-09-17 00:05:25.440 UTC [27] LOG: checkpoint complete: wrote 3 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.201 s, sync=0.055 s, total=0.350 s; sync files=3, longest=0.038 s, average=0.019 s; distance=8 kB, estimate=15 kB 2023-09-17 00:08:48.389 UTC [49] ERROR: could not obtain lock on row in relation "ir_cron" 2023-09-17 00:08:48.389 UTC [49] STATEMENT: SELECT id FROM "ir_cron" WHERE id IN (5) FOR NO KEY UPDATE NOWAIT 2023-09-17 00:10:25.540 UTC [27] LOG: checkpoint starting: time 2023-09-17 00:10:25.850 UTC [27] LOG: checkpoint complete: wrote 3 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.201 s, sync=0.034 s, total=0.310 s; sync files=3, longest=0.017 s, average=0.012 s; distance=8 kB, estimate=14 kB 2023-09-17 00:13:20.188 UTC [1] LOG: received fast shutdown request 2023-09-17 00:13:20.231 UTC [1] LOG: aborting any active transactions 2023-09-17 00:13:20.231 UTC [50] FATAL: terminating connection due to administrator command 2023-09-17 00:13:20.231 UTC [49] FATAL: terminating connection due to administrator command 2023-09-17 00:13:20.231 UTC [39] FATAL: terminating connection due to administrator command 2023-09-17 00:13:20.233 UTC [512] FATAL: terminating connection due to administrator command 2023-09-17 00:13:20.234 UTC [504] FATAL: terminating connection due to administrator command 2023-09-17 00:13:20.234 UTC [464] FATAL: terminating connection due to administrator command 2023-09-17 00:13:20.234 UTC [115] FATAL: terminating connection due to administrator command 2023-09-17 00:13:20.234 UTC [265] FATAL: terminating connection due to administrator command 2023-09-17 00:13:20.235 UTC [511] FATAL: terminating connection due to administrator command 2023-09-17 00:13:20.240 UTC [34] FATAL: terminating connection due to administrator command 2023-09-17 00:13:20.240 UTC [501] FATAL: terminating connection due to administrator command 2023-09-17 00:13:20.240 UTC [75] FATAL: terminating connection due to administrator command 2023-09-17 00:13:20.240 UTC [341] FATAL: terminating connection due to administrator command 2023-09-17 00:13:20.242 UTC [1] LOG: background worker "logical replication launcher" (PID 33) exited with exit code 1 2023-09-17 00:13:20.260 UTC [27] LOG: shutting down 2023-09-17 00:13:20.287 UTC [27] LOG: checkpoint starting: shutdown immediate 2023-09-17 00:13:20.352 UTC [27] LOG: checkpoint complete: wrote 1 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.001 s, sync=0.015 s, total=0.092 s; sync files=1, longest=0.015 s, average=0.015 s; distance=0 kB, estimate=13 kB 2023-09-17 00:13:20.364 UTC [1] LOG: database system is shut down PostgreSQL Database directory appears to contain a database; Skipping initialization 2023-09-17 00:14:53.247 UTC [1] LOG: starting PostgreSQL 15.4 (Debian 15.4-2.pgdg120+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 12.2.0-14) 12.2.0, 64-bit 2023-09-17 00:14:53.281 UTC [1] LOG: listening on IPv4 address "0.0.0.0", port 5432 2023-09-17 00:14:53.281 UTC [1] LOG: listening on IPv6 address "::", port 5432 2023-09-17 00:14:53.562 UTC [1] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432" 2023-09-17 00:14:54.093 UTC [29] LOG: database system was shut down at 2023-09-17 00:13:20 UTC 2023-09-17 00:14:54.144 UTC [30] FATAL: the database system is starting up 2023-09-17 00:14:54.883 UTC [1] LOG: database system is ready to accept connections 2023-09-17 00:16:05.850 UTC [40] ERROR: could not obtain lock on row in relation "ir_cron" 2023-09-17 00:16:05.850 UTC [40] STATEMENT: SELECT id FROM "ir_cron" WHERE id IN (5) FOR NO KEY UPDATE NOWAIT 2023-09-17 00:19:16.764 UTC [41] ERROR: could not obtain lock on row in relation "ir_cron" 2023-09-17 00:19:16.764 UTC [41] STATEMENT: SELECT id FROM "ir_cron" WHERE id IN (5) FOR NO KEY UPDATE NOWAIT 2023-09-17 00:19:54.192 UTC [27] LOG: checkpoint starting: time 2023-09-17 00:20:00.753 UTC [27] LOG: checkpoint complete: wrote 4 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.202 s, sync=2.631 s, total=6.561 s; sync files=5, longest=1.124 s, average=0.527 s; distance=9 kB, estimate=9 kB 2023-09-17 00:23:31.235 UTC [39] ERROR: could not obtain lock on row in relation "ir_cron" 2023-09-17 00:23:31.235 UTC [39] STATEMENT: SELECT id FROM "ir_cron" WHERE id IN (5) FOR NO KEY UPDATE NOWAIT 2023-09-17 00:24:54.852 UTC [27] LOG: checkpoint starting: time 2023-09-17 00:24:56.084 UTC [27] LOG: checkpoint complete: wrote 12 buffers (0.1%); 0 WAL file(s) added, 0 removed, 0 recycled; write=1.103 s, sync=0.062 s, total=1.232 s; sync files=4, longest=0.037 s, average=0.016 s; distance=59 kB, estimate=59 kB 2023-09-17 00:28:48.507 UTC [40] ERROR: could not obtain lock on row in relation "ir_cron" 2023-09-17 00:28:48.507 UTC [40] STATEMENT: SELECT id FROM "ir_cron" WHERE id IN (5) FOR NO KEY UPDATE NOWAIT 2023-09-17 00:29:54.180 UTC [27] LOG: checkpoint starting: time 2023-09-17 00:29:54.547 UTC [27] LOG: checkpoint complete: wrote 3 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.202 s, sync=0.091 s, total=0.367 s; sync files=3, longest=0.073 s, average=0.031 s; distance=10 kB, estimate=54 kB 2023-09-17 00:30:47.930 UTC [1] LOG: received fast shutdown request 2023-09-17 00:30:48.003 UTC [1] LOG: aborting any active transactions 2023-09-17 00:30:48.003 UTC [40] FATAL: terminating connection due to administrator command 2023-09-17 00:30:48.004 UTC [41] FATAL: terminating connection due to administrator command 2023-09-17 00:30:48.004 UTC [35] FATAL: terminating connection due to administrator command 2023-09-17 00:30:48.004 UTC [39] FATAL: terminating connection due to administrator command 2023-09-17 00:30:48.007 UTC [1] LOG: background worker "logical replication launcher" (PID 33) exited with exit code 1 2023-09-17 00:30:48.010 UTC [27] LOG: shutting down 2023-09-17 00:30:48.024 UTC [27] LOG: checkpoint starting: shutdown immediate 2023-09-17 00:30:48.038 UTC [84] FATAL: the database system is shutting down 2023-09-17 00:30:48.092 UTC [27] LOG: checkpoint complete: wrote 0 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.001 s, sync=0.001 s, total=0.083 s; sync files=0, longest=0.000 s, average=0.000 s; distance=0 kB, estimate=48 kB 2023-09-17 00:30:48.096 UTC [1] LOG: database system is shut down PostgreSQL Database directory appears to contain a database; Skipping initialization 2023-09-17 00:30:48.660 UTC [1] LOG: starting PostgreSQL 15.4 (Debian 15.4-2.pgdg120+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 12.2.0-14) 12.2.0, 64-bit 2023-09-17 00:30:48.660 UTC [1] LOG: listening on IPv4 address "0.0.0.0", port 5432 2023-09-17 00:30:48.660 UTC [1] LOG: listening on IPv6 address "::", port 5432 2023-09-17 00:30:48.671 UTC [1] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432" 2023-09-17 00:30:48.726 UTC [29] LOG: database system was shut down at 2023-09-17 00:30:48 UTC 2023-09-17 00:30:48.760 UTC [1] LOG: database system is ready to accept connections ``` This is the docker logs for the database container.
OVERLORD commented 2026-02-05 01:17:59 +03:00
Author
Owner
Copy Link

@Majestic7979 commented on GitHub (Sep 18, 2023):

This was not an immich issue. It was a Watchtower upgrade of the Postgresql container, taking it up to version 16, meaning the new database format that 16 expected was not available, because the DB was v15, so it was not launching. Recreated container with the postgres:15 tag, all back to normal. It would be great if Immich could reconsider using PostgreSQL, why not use MariaDB instead? I never had this issue of database version mismatch after upgrading MariaDB, everything seems to be done automatically and flawlessly.

@Majestic7979 commented on GitHub (Sep 18, 2023): This was not an immich issue. It was a Watchtower upgrade of the Postgresql container, taking it up to version 16, meaning the new database format that 16 expected was not available, because the DB was v15, so it was not launching. Recreated container with the postgres:15 tag, all back to normal. It would be great if Immich could reconsider using PostgreSQL, why not use MariaDB instead? I never had this issue of database version mismatch after upgrading MariaDB, everything seems to be done automatically and flawlessly.
OVERLORD commented 2026-02-05 01:18:03 +03:00
Author
Owner
Copy Link

@etnoy commented on GitHub (Sep 26, 2023):

We have no plans to move from postgres.

@etnoy commented on GitHub (Sep 26, 2023): We have no plans to move from postgres.
OVERLORD commented 2026-02-05 01:18:08 +03:00
Author
Owner
Copy Link

@bo0tzz commented on GitHub (Sep 26, 2023):

To add, you should be very careful about using automatic update tools like watchtower, and always pin your images to specific versions. That goes not only for postgres, but also for example for Immich itself, as upgrades often need you to be aware of changes and perhaps take action.

@bo0tzz commented on GitHub (Sep 26, 2023): To add, you should be very careful about using automatic update tools like watchtower, and always pin your images to specific versions. That goes not only for postgres, but also for example for Immich itself, as upgrades often need you to be aware of changes and perhaps take action.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
accessibility
changelog:enhancement
changelog:security
changelog:translation
cli
date-time
documentation
external-library
format
good first issue
needs-answer
nice to have
sharing
tech-debt
📱mobile
🖥️web
🗄️server
🧠machine-learning
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: immich-app/immich#1334
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?