I’m trying to move the postgres db from Docker to Azure, but I can’t get it to work.
I’m using a managed flexible server in Azure now.
I was able to dump the data in docker, but when importing it in Azure, I’m getting loads of errors about relations not existing/found.
I do see a lot of tables that have been created.
When I update my docker.env with the azure postgres URI and spin everything up, the api container simply won’t start.
In the logs also a lot of errors about missing items.
Does anyone have experience with this? Or better choose a different platform, AWS?
It seems that both Azure and AWS are lacking the superuser role. According to the retool docs, this is required for updates.
Would this be a blocker for using a managed postgres db? Or is there a workaround for this?
I’m curious how other onpremise users configured their db. Maybe a linux vm with postgres installed? Just the standard postgres docker container?
Re: I’m getting loads of errors about relations not existing/found.
If you are following the instructions here, then there are some errors are expected at the beginning of the restore script. This is because we use the -clean command, which attempts to remove existing items before restoring and will generate errors if it's the initial db set up:
Just wanted to clarify which errors you're specifically running into before I lead you down any irrelevant paths!
I was able to resolve this. I had to enable 2 extensions on the postgres server. Pgcrypto and uuid-ossp.
Amazing So glad to hear you were able to get this resolved and thank you for the update! Appreciate it.