#Postgres Setup

1 messages · Page 1 of 1 (latest)

winged hemlock
#

I'm trying to find out what roles/permissions the immich user would need in a postgres database without granting SUPERUSER. Is there a known list of these permissions that immich requires?

warped martenBOT
#

:wave: Hey @winged hemlock,

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. :ballot_box_with_check: verified I'm on the latest release(note that mobile app releases may take some time).
  2. :ballot_box_with_check: read applicable release notes.
  3. :ballot_box_with_check: reviewed the FAQs for known issues.
  4. :ballot_box_with_check: 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.

green owl
#

my apologies, I thought that link had a guide

wide palm
green owl
#

Thats the one, thanks!

winged hemlock
#

That's going to be a little tough then. As pgbouncer doesn't support authenticating users with superuser options.

green owl
winged hemlock
drowsy marsh
valid kettle
#

I don’t really understand your issue. You wouldn’t be using our image if you’re using this guide

winged hemlock
valid kettle
#

Is this some k8s shit? Lol

#

My guess is yes

#

Yeah I don’t know anything about this haha sorry

drowsy marsh
#

You only need ours if you're migrating from pgvecto.rs

#

That said; idk anything about crunchy so can't really help much with that

winged hemlock
#

I have an old installation I am trying to restore still. Think I DM'd you awhile back.

#

At this point I will probably use tensorchord's image then and just clean install.

winged hemlock
# valid kettle My guess is yes

You're good, I didn't expect any support on the setup. Just was confused based on the differing recommendations on what image to be running and why it required to run as root

valid kettle
#

Yes our docs would assume a standard / bare metal Postgres install at least that is what most of us (me) use

#

So I’m sure adapting that can be tricky for declarative config