#Downgrade Postgres

1 messages · Page 1 of 1 (latest)

crimson lark
#

Hey I went to setup my container but didn't see the there was a mismatch between the current version of postgres on SpaceInvader's container and what I see in the docker-compose.yml on github. More specifically, I see the docker-compose has 0.2.0 and I had installed 0.3.0. This is the error I am seeing. What's the best way to resolve this? Thanks!

[Nest] 400  - 03/02/2025, 11:34:56 AM     LOG [Api:EventRepository] Initialized websocket server
Error: The database currently has pgvecto.rs 0.3.0 activated, but the Postgres instance only has 0.2.0 available.
    This most likely means the extension was downgraded.
    If pgvecto.rs 0.3.0 is compatible with Immich, please ensure the Postgres instance has this available.
    at /app/immich/server/dist/services/database.service.js:91:23
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async /app/immich/server/dist/repositories/database.repository.js:211:23
api worker exited with code 1
Starting api worker
icy lilyBOT
#

:wave: Hey @crimson lark,

Thanks for reaching out to us. Please carefully read this message and follow the recommended actions. This will help us be more effective in our support effort and leave more time for building Immich immich.

References

#

Checklist

I have...

  1. :blue_square: verified I'm on the latest release(note that mobile app releases may take some time).
  2. :blue_square: read applicable release notes.
  3. :blue_square: reviewed the FAQs for known issues.
  4. :blue_square: reviewed Github for known issues.
  5. :blue_square: tried accessing Immich via local ip (without a custom reverse proxy).
  6. :blue_square: uploaded the relevant information (see below).
  7. :blue_square: tried an incognito window, disabled extensions, cleared mobile app cache, logged out and back in, different browsers, etc. as applicable

(an item can be marked as "complete" by reacting with the appropriate number)

Information

In order to be able to effectively help you, we need you to provide clear information to show what the problem is. The exact details needed vary per case, but here is a list of things to consider:

  • Your docker-compose.yml and .env files.
  • Logs from all the containers and their status (see above).
  • All the troubleshooting steps you've tried so far.
  • Any recent changes you've made to Immich or your system.
  • Details about your system (both software/OS and hardware).
  • Details about your storage (filesystems, type of disks, output of commands like fdisk -l and df -h).
  • The version of the Immich server, mobile app, and other relevant pieces.
  • Any other information that you think might be relevant.

Please paste files and logs with proper code formatting, and especially avoid blurry screenshots.
Without the right information we can't work out what the problem is. Help us help you ;)

If this ticket can be closed you can use the /close command, and re-open it later if needed.

crimson lark
#

I should also add I'm on the latest version of unRAID

hexed oar
#

0.3.0 should work so easiest is probably just to go back to that

#

Downgrading isn’t realistically possible

crimson lark
#

Understood

#

I nuked the database container and the respective folder in appdata and did it with 0.3.0 and getting a new error:

📎 message.txt
#

Never mind got it running. Had to stop both this and the database and then delete the appdata folder for the database once again, start the database container again, then let immich go