- Currently, during installation, we do not take into account the database table name prefix from env variables during installation (if specified by the user we ignore it and we try to generate a random prefix)
- For me putting that auto-generated random prefix back into environment variables failed after install, causing the installation to die, so I added it in env variables before hand, but that didn't help as we were ignoring it.
Need to set `db_charset` and use it for installation connection to contest `missing index: 'charset'` error.
Error happens on postgresql 10 (and probably previous versions).
