Recommended PostgreSQL version

Get answers to your questions about color grading, editing and finishing with DaVinci Resolve.
  • Author
  • Message
Offline

Michael.Graeve

  • Posts: 2
  • Joined: Tue Sep 25, 2018 10:32 am
  • Location: Erlangen, Germany
  • Real Name: Michael Graeve

Recommended PostgreSQL version

PostThu Mar 25, 2021 8:26 am

Hi,

my database colleagues pointed out, that PostgreSQL 9.5 will no longer be updated:

www postgresql org

--> support --> versioning

(and 9.6 will followed by the end of this year)

Now I searched for quit some time to figure out some hints about using Davinci Resolve 16 with a younger PostgreSQL version but didn't get clear answer yet.

So - what is the recommended PostgreSQL version for
- Davinci 16
- Davinci 17

Any suggestions?

Best regards
Michael
Michael Gräve, MultiMediaZentrum
Friedrich-Alexander-Universität Erlangen-Nürnberg
Regionales Rechenzentrum Erlangen (RRZE)
Martensstraße 1, 91058 Erlangen, Germany
http://www.mmz.rrze.uni-erlangen.de
Offline
User avatar

Dwaine Maggart

Blackmagic Design

  • Posts: 11251
  • Joined: Wed Aug 22, 2012 2:53 pm

Re: Recommended PostgreSQL version

PostFri Mar 26, 2021 11:20 pm

The recommended version is:

Resolve 16: the one the Resolve 16 installer installs.

Resolve 17: The one the Resolve 17 Project Server installer installs.
Dwaine Maggart
Blackmagic Design DaVinci Support
Online

Jim Simon

  • Posts: 29830
  • Joined: Fri Dec 23, 2016 1:47 am

Re: Recommended PostgreSQL version

PostSat Mar 27, 2021 3:46 pm

I love that answer. :lol:
My Biases:

You NEED training.
You NEED a desktop.
You NEED a calibrated (non-computer) display.
Offline

Heikki Repo

  • Posts: 20
  • Joined: Wed Apr 20, 2016 10:48 am
  • Location: Finland

Re: Recommended PostgreSQL version

PostWed May 19, 2021 5:34 pm

Does Resolve 17 depend on some of the fixes added after Postgresql 9.5.17 (I think the installer for Mac and Windows has 9.5.19)? Just asking since updating this software from one minor EOL version to other minor EOL version might not be that simple process on Linux.

I guess BMD's answer is what is said above, but any input from others using Resolve 17 and Postgresql - has 9.5.17 been safe to use or have you all upgraded?
Offline
User avatar

Dwaine Maggart

Blackmagic Design

  • Posts: 11251
  • Joined: Wed Aug 22, 2012 2:53 pm

Re: Recommended PostgreSQL version

PostWed May 19, 2021 7:07 pm

The Resolve 16 Mac installer switched to PostgreSQL 9.5.19 starting with Resolve version 16.1.

This was required for proper support in Catalina and Big Sur.

This is still the version that the Mac Resolve 17 Project Server app would install.

The Resolve 17 Windows Project Server app still installs PostgreSQL 9.5.4.

Do note that none of the above installers will install PostgreSQL if they detect it's already installed on the system.
Dwaine Maggart
Blackmagic Design DaVinci Support
Offline

peterjackson

  • Posts: 1144
  • Joined: Sat Aug 18, 2018 7:12 pm
  • Real Name: Peter Jackson

Re: Recommended PostgreSQL version

PostWed May 19, 2021 7:39 pm

PostgreSQL really doesn't do back compatibility breaks usually. Even the latest version 13 likely will work just fine and perform much faster. Version 9 is from the stone age.
5950x, 3090, 128GB.
Offline
User avatar

Elliott Balsley

  • Posts: 618
  • Joined: Sat Oct 13, 2012 5:45 pm
  • Location: Southern California

Re: Recommended PostgreSQL version

PostTue Sep 28, 2021 6:22 pm

Peter, have you actually tried version 13? I'm going to stand up a server for testing soon and I'll be interested to see if there's any performance difference between 9 and something newer.
Offline
User avatar

Olivier MATHIEU

  • Posts: 865
  • Joined: Thu Aug 04, 2016 1:55 pm
  • Location: Paris/Grenoble, FRANCE

Re: Recommended PostgreSQL version

PostThu Oct 07, 2021 8:49 am

Elliott Balsley wrote:Peter, have you actually tried version 13? I'm going to stand up a server for testing soon and I'll be interested to see if there's any performance difference between 9 and something newer.

Have you noticed any difference ?

I installed lastest PosgreSQL version (14 I think) on The QNAP and seems to work fine
Resolve Studio 18.6.x & Fusion Studio 18.6.x | MacOS 13.6.x | GUI : 3840 x 2160 | Ntw : 10Gb/s
MacbookPro M2 Max
Offline
User avatar

Dwaine Maggart

Blackmagic Design

  • Posts: 11251
  • Joined: Wed Aug 22, 2012 2:53 pm

Re: Recommended PostgreSQL version

PostThu Oct 07, 2021 9:46 pm

@Olivier: Are you sure about that?

It's been reported by one party and confirmed by another that PostgreSQL versions above 11 won't work with Resolve.

Apparently because the adsrc column was removed in Postgres 12.
Dwaine Maggart
Blackmagic Design DaVinci Support
Offline
User avatar

Olivier MATHIEU

  • Posts: 865
  • Joined: Thu Aug 04, 2016 1:55 pm
  • Location: Paris/Grenoble, FRANCE

Re: Recommended PostgreSQL version

PostTue Jan 04, 2022 2:46 pm

Dwaine Maggart wrote:@Olivier: Are you sure about that?

It's been reported by one party and confirmed by another that PostgreSQL versions above 11 won't work with Resolve.

Apparently because the adsrc column was removed in Postgres 12.


I'll try soon a new install with postgresSQL 14 on container station
I'll keep you update
Resolve Studio 18.6.x & Fusion Studio 18.6.x | MacOS 13.6.x | GUI : 3840 x 2160 | Ntw : 10Gb/s
MacbookPro M2 Max
Offline
User avatar

Dwaine Maggart

Blackmagic Design

  • Posts: 11251
  • Joined: Wed Aug 22, 2012 2:53 pm

Re: Recommended PostgreSQL version

PostTue Jan 04, 2022 4:06 pm

That's now old info. As of Resolve 17.4, it supports newer PostgreSQL versions.
Dwaine Maggart
Blackmagic Design DaVinci Support
Offline

mpetech

  • Posts: 728
  • Joined: Wed Sep 04, 2013 9:52 pm
  • Real Name: Dom Silverio

Re: Recommended PostgreSQL version

PostTue Jan 04, 2022 5:07 pm

Dwaine Maggart wrote:That's now old info. As of Resolve 17.4, it supports newer PostgreSQL versions.


Up to what version does DR supports now?
Offline
User avatar

Olivier MATHIEU

  • Posts: 865
  • Joined: Thu Aug 04, 2016 1:55 pm
  • Location: Paris/Grenoble, FRANCE

Re: Recommended PostgreSQL version

PostWed Jan 05, 2022 10:44 am

Dwaine Maggart wrote:That's now old info. As of Resolve 17.4, it supports newer PostgreSQL versions.

Okay
Unfortunately i don't succeed to install PostgreSQL 14 on the Quhero 5
but the PostgreSQL 11 seems to work correctly
Resolve Studio 18.6.x & Fusion Studio 18.6.x | MacOS 13.6.x | GUI : 3840 x 2160 | Ntw : 10Gb/s
MacbookPro M2 Max
Offline
User avatar

Olivier MATHIEU

  • Posts: 865
  • Joined: Thu Aug 04, 2016 1:55 pm
  • Location: Paris/Grenoble, FRANCE

Re: Recommended PostgreSQL version

PostWed Jan 05, 2022 10:45 am

mpetech wrote:Up to what version does DR supports now?

+1
Resolve Studio 18.6.x & Fusion Studio 18.6.x | MacOS 13.6.x | GUI : 3840 x 2160 | Ntw : 10Gb/s
MacbookPro M2 Max
Offline
User avatar

Dwaine Maggart

Blackmagic Design

  • Posts: 11251
  • Joined: Wed Aug 22, 2012 2:53 pm

Re: Recommended PostgreSQL version

PostTue Jan 11, 2022 2:05 am

I would assume, based on what I'm told, through the current 14.1 version. But I have not personally tested that version. Or any version above 11.

@Olivier: What is Quhero 5? Is that a NAS of some sort? Running Linux? And version 11 works on that system?
Dwaine Maggart
Blackmagic Design DaVinci Support
Offline
User avatar

Dwaine Maggart

Blackmagic Design

  • Posts: 11251
  • Joined: Wed Aug 22, 2012 2:53 pm

Re: Recommended PostgreSQL version

PostTue Jan 11, 2022 3:21 am

OK, I downloaded and installed the PostgreSQL 14.1 installer for Windows, and installed it on a Windows 11 PC.

I used the default Resolve postgres password of DaVinci when asked for the postgres pw.

I launched Resolve Studio 17.4.3 on the same machine, and created a new PostgreSQL database using all the PostgreSQL New Database defaults (Location 127.0.0.1, Username postgres, Password DaVinci) and gave it a name of v17. It created the database with no issue.

I copied projects from the Disk database to the new v17 PostgreSQL db. It all works fine.

I then tried making a backup of the db. The first time I ran a backup, it asked me to point to the PostgreSQL bin directory. I did that. It made the backup.

I then Restored the backup, to a new db called v17v2. That worked without issue.

I also tested Optimize. That also worked.

So as far as I can tell, PostgreSQL 14.1 works fine with Resolve 17.4.3. At least on a Windows system.

I also installed the Resolve 17.4.1 Project Server app on the same PC. On the installer, I unchecked the option to install PostgreSQL 9.5.4. After the Project Server install completed, launched it, and it doesn't see the PostgreSQL 14.1 install. It requests you run the Project Server installer again, and check the PostgreSQL 9.5.4 install option.

So, it looks like the Project Server app is only going to work with a PostgreSQL 9.5.4 install.

Now, if you wanted to access that 14.1 v17 database from ANOTHER Resolve system, and since you can't use the Project Server app to Share the db, you'd need to manually edit the pg_hba.conf file in the PostgreSQL 14 data folder, to allow whatever level of outside access you desired. Then you'd need to restart PostgreSQL after making the pg_hba.conf change.
Dwaine Maggart
Blackmagic Design DaVinci Support
Offline
User avatar

Olivier MATHIEU

  • Posts: 865
  • Joined: Thu Aug 04, 2016 1:55 pm
  • Location: Paris/Grenoble, FRANCE

Re: Recommended PostgreSQL version

PostTue Jan 11, 2022 4:59 pm

Thanks for all those informations

QuHero Is QNAP "Pro" Operating System ...
I'll try again with PostgreSQL version 14.1And report
Have a nice day
Resolve Studio 18.6.x & Fusion Studio 18.6.x | MacOS 13.6.x | GUI : 3840 x 2160 | Ntw : 10Gb/s
MacbookPro M2 Max
Offline
User avatar

Dwaine Maggart

Blackmagic Design

  • Posts: 11251
  • Joined: Wed Aug 22, 2012 2:53 pm

Re: Recommended PostgreSQL version

PostTue Jan 11, 2022 6:36 pm

If PostgreSQL is running on a QNAP NAS, you'll definitely need to ensure you've properly modified pg_hba.conf to allow remote access to PostgreSQL.
Dwaine Maggart
Blackmagic Design DaVinci Support
Offline
User avatar

Olivier MATHIEU

  • Posts: 865
  • Joined: Thu Aug 04, 2016 1:55 pm
  • Location: Paris/Grenoble, FRANCE

Re: Recommended PostgreSQL version

PostFri Jan 14, 2022 5:27 pm

Dwaine Maggart wrote:If PostgreSQL is running on a QNAP NAS, you'll definitely need to ensure you've properly modified pg_hba.conf to allow remote access to PostgreSQL.

Yep
it is describe here https://www.qnap.com/en/how-to/tutorial/article/how-can-i-collaborate-davinci-resolve-studio-16-between-macos-and-windows-in-qts-4-4-3
Resolve Studio 18.6.x & Fusion Studio 18.6.x | MacOS 13.6.x | GUI : 3840 x 2160 | Ntw : 10Gb/s
MacbookPro M2 Max
Offline
User avatar

Olivier MATHIEU

  • Posts: 865
  • Joined: Thu Aug 04, 2016 1:55 pm
  • Location: Paris/Grenoble, FRANCE

Re: Recommended PostgreSQL version

PostWed Jan 19, 2022 9:23 pm

I've just install PostgreSQL 14.1on my QNAP
Creating a database is OK
Importing project is OK
Modifying Project is OK
Resolve Studio 18.6.x & Fusion Studio 18.6.x | MacOS 13.6.x | GUI : 3840 x 2160 | Ntw : 10Gb/s
MacbookPro M2 Max
Offline
User avatar

Glenn Venghaus

  • Posts: 1358
  • Joined: Wed Jan 01, 2014 9:56 pm
  • Location: Amsterdam , The Netherlands

Re: Recommended PostgreSQL version

PostSat Jan 22, 2022 12:34 pm

Working since a few weeks with latest resolve using my new 14.1 based posgresql custom dockers that replaced the 9.6 versions and zero issues.
Keep in mind that if you have monitoring / backup / multi node replication scripts etc setup, that several db parameters have changed . For example *xlog* parameters have been replaced by *wal* parameters. So check the documentation and adjust.
Beatstep & APC-40 Resolve Edition Controllers https://posttools.tachyon-consulting.com
Test Rig : 2xXeon (24c) | UNRAID KVM OSX VM's | 128GB | 5700XT | 40Gbe
Prod Rig : i9-7940X (14c) | OSX 10.15 | 64GB | 2xVega 56 | 40Gbe | Tb3 | V:Eizo | A:5.1RME
Offline

juliandarley

  • Posts: 76
  • Joined: Mon May 07, 2018 7:11 pm
  • Real Name: Julian Darley

Re: Recommended PostgreSQL version

PostMon Jan 31, 2022 3:10 pm

Dwaine Maggart wrote:OK, I downloaded and installed the PostgreSQL 14.1 installer for Windows, and installed it on a Windows 11 PC.
I launched Resolve Studio 17.4.3 on the same machine, and created a new PostgreSQL database using all the PostgreSQL New Database defaults (Location 127.0.0.1, Username postgres, Password DaVinci) and gave it a name of v17. It created the database with no issue.
I copied projects from the Disk database to the new v17 PostgreSQL db. It all works fine.
Now, if you wanted to access that 14.1 v17 database from ANOTHER Resolve system, and since you can't use the Project Server app to Share the db, you'd need to manually edit the pg_hba.conf file in the PostgreSQL 14 data folder, to allow whatever level of outside access you desired. Then you'd need to restart PostgreSQL after making the pg_hba.conf change.


hi dwaine, i have got Resolve to work with ubuntu postgres 9.6, but not with any of pg11, pg12, or pg14.1. i can see that Resolve is trying to create the database but then it always crashes.

i wondered if you or anyone else had got Resolve (in my case running on windows 10) working with postgresql on ubuntu? i have changed the pg_hba.conf (for all versions of PG).

Resolve logs show that resolve seems to be connecting to PG14 but is getting stuck at Fairlight. indeed when i try to launch Resolve (it crashes during connection with PG14.1), Resolve quits unexpectedly during the Fairlight phase (this is also true with pg11 and pg12). i can switch back to PG9.6, but it is EOL and i really don't think it is good to use an unsupported server, especially as we are planning to edit a feature film on it.
Last edited by juliandarley on Mon Jan 31, 2022 6:01 pm, edited 1 time in total.
Resolve Studio 18.5 & Fusion Studio 18
main deskstop: Windows 10 Pro 64bit v2004
Core i7-6700K 4GHz with 64GB RAM
GTX 1080
BMD Cloud Project Server & network Project Server on Windows 10
Offline
User avatar

Dwaine Maggart

Blackmagic Design

  • Posts: 11251
  • Joined: Wed Aug 22, 2012 2:53 pm

Re: Recommended PostgreSQL version

PostMon Jan 31, 2022 5:40 pm

What Resolve version are you using?
Dwaine Maggart
Blackmagic Design DaVinci Support
Offline

juliandarley

  • Posts: 76
  • Joined: Mon May 07, 2018 7:11 pm
  • Real Name: Julian Darley

Re: Recommended PostgreSQL version

PostMon Jan 31, 2022 6:03 pm

the latest: studio 17.4.3 (on Win 10, v2004)
Resolve Studio 18.5 & Fusion Studio 18
main deskstop: Windows 10 Pro 64bit v2004
Core i7-6700K 4GHz with 64GB RAM
GTX 1080
BMD Cloud Project Server & network Project Server on Windows 10
Offline
User avatar

Dwaine Maggart

Blackmagic Design

  • Posts: 11251
  • Joined: Wed Aug 22, 2012 2:53 pm

Re: Recommended PostgreSQL version

PostMon Jan 31, 2022 10:32 pm

I haven't tested PostgreSQL on Ubuntu. PostgreSQL is PostgreSQL. It works on CentOS 7.9, so it ought to work the same on any distro. Therefore, my first hunch would be an issue with how it's installed on Ubuntu.

I'll try to check it on Ubuntu in my spare time...
Dwaine Maggart
Blackmagic Design DaVinci Support
Offline

juliandarley

  • Posts: 76
  • Joined: Mon May 07, 2018 7:11 pm
  • Real Name: Julian Darley

Re: Recommended PostgreSQL version

PostMon Jan 31, 2022 11:27 pm

many thanks. i do have PG9.6 working on two ubuntu installations (v20.04.3 LTS) without a problem, one is a VM and the other is a full physical machine. both work fine. it is only the higher PG versions that don't work, and one can see that Resolve is connecting and creating the database on PG, but then it crashes, i suspect, always at the same place.

i have just checked the databases with dbeaver on my windows desktop and i can see that before it crashed, resolve has indeed created all the tables needed. i feel that i am very close to getting this working.
Resolve Studio 18.5 & Fusion Studio 18
main deskstop: Windows 10 Pro 64bit v2004
Core i7-6700K 4GHz with 64GB RAM
GTX 1080
BMD Cloud Project Server & network Project Server on Windows 10
Offline
User avatar

Glenn Venghaus

  • Posts: 1358
  • Joined: Wed Jan 01, 2014 9:56 pm
  • Location: Amsterdam , The Netherlands

Re: Recommended PostgreSQL version

PostTue Feb 01, 2022 6:42 am

Interestingly enough , when i tried to upgrade my custom docker based postgresl a few weeks back to 14.1, which had ubunto as base image , i had a similar issue. The database was fully created by Resolve but then after that immediate crash. Could not find the cause in the logs and did not want to waste too much time on it , so i ditched that plan and moved to an official Centos Debian/ postgresql14.1 based docker as a base for my own custom dockers and there it woked without a hitch. So there is something there maybe in combination with Ubuntu.
Or just pure coincidence als is definatley a high ranked option.
Last edited by Glenn Venghaus on Tue Feb 01, 2022 9:48 am, edited 1 time in total.
Beatstep & APC-40 Resolve Edition Controllers https://posttools.tachyon-consulting.com
Test Rig : 2xXeon (24c) | UNRAID KVM OSX VM's | 128GB | 5700XT | 40Gbe
Prod Rig : i9-7940X (14c) | OSX 10.15 | 64GB | 2xVega 56 | 40Gbe | Tb3 | V:Eizo | A:5.1RME
Offline

juliandarley

  • Posts: 76
  • Joined: Mon May 07, 2018 7:11 pm
  • Real Name: Julian Darley

Re: Recommended PostgreSQL version

PostTue Feb 01, 2022 9:21 am

Glenn Venghaus wrote: when i tried to upgrade my custom docker based postgresl a few weeks back to 14.1, which had ubunto as base image , i had a similar issue. The database was fully created by Resolve but then after that immediate crash. i ditched that plan and moved to an official Centos / postgresql14.1 based docker as a base for my own custom dockers and there it woked without a hitch. So there is something there maybe in combination with Ubuntu.

thanks for this info, glenn. i have just started using docker in the last week. it's a bit of a paradigm shift (eg. still trying to figure out why one cannot ssh into a docker container) but i shall aim to try out your suggestion of docker + centos + pg14 asap (i wonder if that won't run on an ubuntu host because docker needs the right subsystem for vital services? - i will check this). ironic that centos 7 itself is an EOL of an EOL product! i wish BM would give an indication of when they are going to switch to up-to-date versions of vital products.

i will also call BMD tech support UK this morning and update them on the latest messages here.

update: it looks like a docker container only uses the linux kernel so it doesn't care which distro is the host. will try this out ASAP.
Resolve Studio 18.5 & Fusion Studio 18
main deskstop: Windows 10 Pro 64bit v2004
Core i7-6700K 4GHz with 64GB RAM
GTX 1080
BMD Cloud Project Server & network Project Server on Windows 10
Offline
User avatar

Glenn Venghaus

  • Posts: 1358
  • Joined: Wed Jan 01, 2014 9:56 pm
  • Location: Amsterdam , The Netherlands

Re: Recommended PostgreSQL version

PostTue Feb 01, 2022 9:41 am

p.s. If you start messing with docker for databases, make 10000% sure you understand how dockers and persistant storage works. If you dont understand dockers , stay away untill you do or risk loosing your entire database(s) when the docker rebuilds on an update/change.

I am building my own custom dockers , but this is the official repo for postgresql (which i also used as a base to build on) : https://hub.docker.com/_/postgres

I recommend picking a tag other then latest to "pin" your version to one you want and have it stay there. (for example "14.1" or "14.1-bullseye" etc etc)
You upgrade when you want to and not when the image source is updated (latest).

Lastly: Sorry for the confusion but i did not use a centos base but debian base (as in the official image). The centos was an old experiment that stuck in my brain.
Beatstep & APC-40 Resolve Edition Controllers https://posttools.tachyon-consulting.com
Test Rig : 2xXeon (24c) | UNRAID KVM OSX VM's | 128GB | 5700XT | 40Gbe
Prod Rig : i9-7940X (14c) | OSX 10.15 | 64GB | 2xVega 56 | 40Gbe | Tb3 | V:Eizo | A:5.1RME
Offline
User avatar

Dwaine Maggart

Blackmagic Design

  • Posts: 11251
  • Joined: Wed Aug 22, 2012 2:53 pm

Re: Recommended PostgreSQL version

PostTue Feb 01, 2022 7:51 pm

I can confirm that there is an issue with PostgreSQL on Ubuntu. I installed PostgreSQL 13.5 on an Ubuntu 21.04 system and in Resolve, created a PostgreSQL db, and Resolve crashes upon completion. And crashes when you launch it after that.

In ~/.local/share/DaVinciResolve/configs is a file called .dblist

In the file is a list of databases Resolve has connected to. The last database connected to has an * in the path. The db with the * is the one Resolve will try to use when launched. If you edit the file and remove the *, then Resolve will use the first db in the list, which is the default Disk db.

Doing that allowed me to launch Resolve and see that the database had been created, but selecting it crashed.

I then repeated the process and imported a PostgreSQL db backup from another system. That worked. I could select that and access projects. I could now also access the PostgreSQL db I had previously created on the system.

All the PostgreSQL dbs work fine at that point. But if I create another new PostgreSQL, it crashes. And if I exit Resolve with a PostgreSQL db selected, it will crash when launched. Then I have to remove the * from the .dblist file to be able to launch again.

I have not figured out what it is about the Ubuntu distro that's causing this issue. Open to suggestions.
Dwaine Maggart
Blackmagic Design DaVinci Support
Offline
User avatar

Glenn Venghaus

  • Posts: 1358
  • Joined: Wed Jan 01, 2014 9:56 pm
  • Location: Amsterdam , The Netherlands

Re: Recommended PostgreSQL version

PostTue Feb 01, 2022 8:01 pm

Thanks for confirming that we where not crazy :lol:
Must be something wierd.
Was initialy looking into codepage stuff as that can mess you up in postgresql , but i was not in a patient mode so moved on. But interested as well if you find the cause.

p.s. i do remember switching postgresql to the highest trace level to see if it was an error on the db side, but all i saw was unexpected client connection termination in the logs , so it must be resolve tripping up over something and ungracefully saying goodbye to the db server.
Beatstep & APC-40 Resolve Edition Controllers https://posttools.tachyon-consulting.com
Test Rig : 2xXeon (24c) | UNRAID KVM OSX VM's | 128GB | 5700XT | 40Gbe
Prod Rig : i9-7940X (14c) | OSX 10.15 | 64GB | 2xVega 56 | 40Gbe | Tb3 | V:Eizo | A:5.1RME
Offline

eroncardoso

  • Posts: 3
  • Joined: Wed Apr 08, 2020 6:54 pm
  • Real Name: Eron Aguiar

Re: Recommended PostgreSQL version

PostThu Mar 31, 2022 11:34 pm

Just to let you know,
postgres 14.2, ubuntu server 22.02, Davinci Resolve 17.4.6, are working fine together.
At first the db was not connecting, then I changed the connection method in pg_hba to PASSWORD:
host all all 0.0.0.0/0 password
yes, i know, it means that the password is unencrypted(postgres/DaVinci).
Offline
User avatar

Glenn Venghaus

  • Posts: 1358
  • Joined: Wed Jan 01, 2014 9:56 pm
  • Location: Amsterdam , The Netherlands

Re: Recommended PostgreSQL version

PostSat Apr 02, 2022 7:42 am

Good info !!!.
So looks like something in the password encryption method in combination with Ubuntu may have broken, which explains the behavior that you can create, but then not connect afterwards.

Cant test myself anymore as running on Debian bullseye, but am sure BM can use this info to find/adress the issue.
Beatstep & APC-40 Resolve Edition Controllers https://posttools.tachyon-consulting.com
Test Rig : 2xXeon (24c) | UNRAID KVM OSX VM's | 128GB | 5700XT | 40Gbe
Prod Rig : i9-7940X (14c) | OSX 10.15 | 64GB | 2xVega 56 | 40Gbe | Tb3 | V:Eizo | A:5.1RME
Offline
User avatar

Glenn Venghaus

  • Posts: 1358
  • Joined: Wed Jan 01, 2014 9:56 pm
  • Location: Amsterdam , The Netherlands

Re: Recommended PostgreSQL version

PostSat Apr 02, 2022 7:47 am

p.s. A related suggestion for BM while we are at the topic is to adress the long standing "feature" where when Resolve has an issue connecting to a postgres db , it tends to hard crash instead of just telling us kindly that there is an issue with the db.
Now you have to hack the db definition out of the file to be able to boot resolve.
Its super rare you hit this sort of thing , thats surely why it was understandable never high on the todo list, but nice messages instead of hard crashes are always the preferred way ;-)
And if you are looking into this area anyway.........
Beatstep & APC-40 Resolve Edition Controllers https://posttools.tachyon-consulting.com
Test Rig : 2xXeon (24c) | UNRAID KVM OSX VM's | 128GB | 5700XT | 40Gbe
Prod Rig : i9-7940X (14c) | OSX 10.15 | 64GB | 2xVega 56 | 40Gbe | Tb3 | V:Eizo | A:5.1RME
Offline

Albert Hofmann

  • Posts: 70
  • Joined: Wed Feb 24, 2016 10:01 am

Re: Recommended PostgreSQL version

PostWed Apr 13, 2022 2:22 pm

Dwaine Maggart wrote:I can confirm that there is an issue with PostgreSQL on Ubuntu. I installed PostgreSQL 13.5 on an Ubuntu 21.04 system and in Resolve, created a PostgreSQL db, and Resolve crashes upon completion. And crashes when you launch it after that.
...
I have not figured out what it is about the Ubuntu distro that's causing this issue. Open to suggestions.


Have you checked the PostgreSQL logs on the server? In Debian/Ubuntu, they are under
"/var/log/postgresql/"

You can increase the logging detail by editing
"/etc/postgresql/$YourPGversion/main/postgresql.conf"

Or you could use "tcpdump" to see the communication between Resolve and Postgres.
Offline

Albert Hofmann

  • Posts: 70
  • Joined: Wed Feb 24, 2016 10:01 am

Re: Recommended PostgreSQL version

PostWed Apr 13, 2022 3:45 pm

Since I have an Ubuntu machine with Postgres, I was curious and just tried it. Indeed, it crashes after creating the DB, and cannot be started on that DB. But if Resolve is started with another DB, the "bad" DB actually works and can be used.

I don't know where such bugs can be reported, so I'll just write the details here, and hopefully BM sees it and can fix it. Since everything seems to work after the initial crash, it might be easy to fix?

My PostgreSQL server is Ubuntu 20.04.4, with PostgreSQL version 12.9.

Resolve is Studio v. 17.4.6 build 4 on Windows 10 20H2.

The database gets created. Nothing appears in the Postgres log which is set to the default "log_min_messages = warning".

The last lines in the Resolve log ("%APPDATA%\Roaming\Blackmagic Design\DaVinci Resolve\Support\logs\ResolveDebug.txt") are

Code: Select all
[0x00002b4c] | BtCommon             | INFO  | 2022-04-13 16:42:38,278 | Starting Daemon: C:/Program Files/Blackmagic Design/DaVinci Resolve/DaVinciPanelDaemon.exe
SY panel handler thread starts: 00002660
[0x0000072c] | DbCommon2            | INFO  | 2022-04-13 16:42:38,516 | postgres database test_res_ubu_12192.168.81.198 version 12.9 (Ubuntu 12.9-0ubuntu0.20.04.1)

==========[CRASH DUMP]==========
#TIME Wed Apr 13 16:42:38 2022 - Uptime 00:00:03 (hh:mm:ss)
#PROGRAM_NAME DaVinci Resolve Studio v17.4.6.0004 (Windows/MSVC x86_64)
#BMD_ARCHITECTURE x86_64
#BMD_BUILD_UUID 60c1656b-7224-4553-be5e-126310d247c1
#BMD_GIT_COMMIT 02202f962b16f0d0e861d9284b1b1dcb10a68182
#BMD_UTIL_VERSION 17.4.6.0004
#OS Windows

00007FF739308CEC
00000180A0750324
00007FFCCA2DB86B
0000000000700074
00000000000000A1
0000005F89B1CF90
00007FF739308C40
00007FFCBB8EE6E0

================================


After editing "%APPDATA%\Roaming\Blackmagic Design\DaVinci Resolve\Preferences\dblist.conf" to let Resolve start with it's normal DB, it does start and shows the new DB.

Then it can be selected, and seems to work fine. I copied a small test project from our normal DB (PG v. 9.6 on CentOS) to the new PG 12.9 on Ubuntu, and could open the project.

However, at the next restart of Resolve with the new DB as default, it crashed again. It also left two ".dmp" files in ...\Support\logs\, one of 3 MB. and another of 467 MB.

The PostgreSQL server log just had:

Code: Select all
2022-04-13 17:33:59.411 CEST [43937] postgres@test_res_ubu_12 LOG:  could not receive data from client: Connection reset by peer
Offline

lucanos

  • Posts: 2
  • Joined: Fri Feb 18, 2022 3:52 am
  • Real Name: Luke Stevenson

Re: Recommended PostgreSQL version

PostThu Apr 14, 2022 6:11 am

I'm also having significant issues trying to connect Davinci Resolve to a remote PostgreSQL Server.

Server Details:
  • Ubuntu v20.04.4 LTS
  • PostgreSQL v14.2 (latest)

Client Details:
  • Windows 10 (OS Build 19042.1586)
  • Davinci Resolve v17.4.60004

Actions:
  1. Installed Ubuntu, PostgreSQL, etc.
  2. Confirmed able to remotely connect to PostgreSQL using pgAdmin 4
  3. Installed Davinci Resolve
  4. Attempted to "Connect Database" using proved PostgreSQL credentials
  5. Tailing PostgreSQL Log on Server, can see Resolve connects to the Database and Creates Tables
  6. Resolve freezes
  7. Force close Resolve
  8. Resolve crashes on launch, unless internet connection turned off (forcing it to connect to Local Database)
  9. Disconnect Remote PostgreSQL Database in Resolve
  10. Attempt to "Connect Database" (to a proven Database, which has 145 tables, so Resolve was able to create these tables during earlier connection)
  11. Resolve freezes

I have turned up logging on my PostgreSQL server, and I can see that Resolve is connecting to the Server, and is running a large number of queries when launched.
The last query before the splash screen goes to "Loading Fairlight Engine" and then subsequently crashes is:
Code: Select all
SELECT "SysId" FROM "Sm2SysIdEntry" LEFT JOIN pg_stat_activity ON "Sm2SysIdEntry"."ClientAddr" = host(pg_stat_activity.client_addr) WHERE pg_stat_activity.client_addr IS NULL AND "Sm2SysIdEntry"."ClientAddr" IS NOT NULL


I am not sure why Resolve is crashing here.

The Server is good. The Database is there. The Connection is proven. But for some reason is crashes when loading the Fairlight Engine if connected to a remote Database.

Happy to provide more information as needed. Not sure if what I have found thusfar is of interest.
Offline

Albert Hofmann

  • Posts: 70
  • Joined: Wed Feb 24, 2016 10:01 am

Re: Recommended PostgreSQL version

PostThu Apr 14, 2022 12:37 pm

I just tried your query directly in my PG 12.9 database which was created yesterday by Resolve. The query does work normally:

Code: Select all
# SELECT "SysId" FROM "Sm2SysIdEntry" LEFT JOIN pg_stat_activity ON "Sm2SysIdEntry"."ClientAddr" = host(pg_stat_activity.client_addr) WHERE pg_stat_activity.client_addr IS NULL AND "Sm2SysIdEntry"."ClientAddr" IS NOT NULL;
    SysId     
--------------
 48 fcf4460b2
(1 row)


So, what is Resolve doing after it received a reply to it's last query?
Offline
User avatar

Dwaine Maggart

Blackmagic Design

  • Posts: 11251
  • Joined: Wed Aug 22, 2012 2:53 pm

Re: Recommended PostgreSQL version

PostThu Apr 14, 2022 4:29 pm

Provide a Resolve log from the Windows client, and provide the pg_log folder log files from PostgreSQL.

Generate the Resolve log with the Resolve Help menu: Create Diagnostics Log on Desktop.
Dwaine Maggart
Blackmagic Design DaVinci Support
Offline

labor4

  • Posts: 18
  • Joined: Sun Feb 16, 2020 4:25 pm
  • Real Name: Manuel Weber

Re: Recommended PostgreSQL version

PostThu Apr 21, 2022 3:15 am

maybe of help, regarding the md5 problem.
I could achieve a persistent connection as far as the tests below. Further tests/info needed.
Currently all is on the md5 method.

- I went up to Ubuntu 22.04 (thanks @eroncardoso).
- DR is 17.4.6 on latest Centos 7.9
- fresh install Postgres 14 on Ubuntu, at first no modif to pg_hba.conf
- note: I don't use the "postgres" user in DR, but a separate one, with all perms.

# sidestep
# unclear why this worked if you read on below
# it may be because I updated the pg client on Centos beforehand
- Created DB via pgAdmin, create DR user/pass
- CONNECTED from DR to empty DB, it initialized it.
- I could restart DR and connect again

# Restore
- deleted previous DR DB via pgAdmin (from the sidestep above)
- Restore from DB9.5.backup from DR to Postgres14
- false GUI error "DB already exists", but DR log complained along the lines "scram-sha-256 not possible without libpg-10 or newer"
- I went on to change the server instead of installing libpg
- "password_encryption = md5" in /etc/postgresql/14/main/postgresql.conf
- change all "scram" methods in pg_hba.conf to md5
- restart postgres server
- DR not worky: scram method was still mandatory (DR logs)
- set new mainuser (postgres) pw, via SQL "ALTER USER postgres PASSWORD 'myPassword';" (wouldn't work without)
- used pgAdmin to overwrite the DR DB user with the same PW it had before (not sure if needed)
- the restore worked, the scram method was not mandatory anymore.
- I could restart DR, connect again, open the 9.5 projects, edit and save.

I don't know the DB internals, but it may be that changing pg_hba.conf to "md5" or even "password" was not enough, because the default method had to me changed as well.
And it seems to me that the "ALTER USER" somehow initialized this default.

So this would ask the question if it had worked on Ubuntu 20.04 too, if this change had been made there also.

Somebody could check on PG14 on Ubuntu20.04: /etc/postgresql/14/main/postgresql.conf for "password_encryption = md5"?
And if not md5: follow above procedure?

Ps: libpg seems to be in package "devel" of the postgres client
Offline

Albert Hofmann

  • Posts: 70
  • Joined: Wed Feb 24, 2016 10:01 am

Re: Recommended PostgreSQL version

PostWed Apr 27, 2022 11:43 am

After a lot more testing, it seems that this problem is specific to Ubuntu 20.04, and Resolve.

I upgraded from Resolve 17 to 18 in the hope that it might have been fixed, but it's still the same. Searching for Ubuntu specific bugs with Postgres, I could not find anything.

So, if your PostgreSQL server is running Ubuntu 20.04, you must use Postgres v. 9.6. It can be installed from the Postgres repositories.

I tried versions 10, 11, and the default 12.9 and all made Resolve crash. The full logs are too big to be uploaded here (let me know if I should upload them elsewhere). But the parts that seem relevant are:

On the Postgres side, after Resolve created the database, there is just "could not receive data from client: Connection reset by peer" as already mentioned.

On the Resolve side, here is an example from logs\LogArchive\ResolveDebug_C1.txt :
Code: Select all
[0x00002d0c] | DbCommon2            | INFO  | 2022-04-26 19:00:52,806 | postgres database res18_on_ubu_pg10 at x270 version 10.20 (Ubuntu 10.20-1.pgdg20.04+1)
Printing Stack Info
00007FF60EA101FC
000000C8AB0F9E50
000000C8AB0F99D0
[0x00002d0c] | DbCommon2            | INFO  | 2022-04-26 19:00:52,825 | Project library [res18_on_ubu_pg10x270] current version <18.0.0.001> updated on <2022-04-26T18:21:02.832>, remark: <patched with 18.0.0.001 database upgrade>

==========[CRASH DUMP]==========
#TIME Tue Apr 26 19:00:52 2022 - Uptime 00:00:24 (hh:mm:ss)
#PROGRAM_NAME DaVinci Resolve v18.0.0b.0007 (Windows/MSVC x86_64)
#BMD_ARCHITECTURE x86_64
#BMD_BUILD_UUID 9509b424-f8da-4d39-81c3-982f5840263a
#BMD_GIT_COMMIT 2ee8a4a68cccc39abeaaec44f4f24648d3df114b
#BMD_UTIL_VERSION 18.0.0b.0007
#OS Windows

00007FF60EA101FC
0000000000000210
00007FFC3FC3B86B
000000000002000A
000000000000006F
000000C8AB0F7E70
00007FF60EA10150
00007FFC2351E6E0

================================


But others reported that with the new Ubuntu 22.04, it works.

And I also tested on Debian v.10 ("Buster") which comes with PostgreSQL v. 11, and that also seemed to work.

(Note also that any possible password/md5 problem would have been irrelevant in my tests because I just used "trust" for my LAN in the pg_hba.conf file, so no password was needed)
Offline

labor4

  • Posts: 18
  • Joined: Sun Feb 16, 2020 4:25 pm
  • Real Name: Manuel Weber

Re: Recommended PostgreSQL version

PostWed Apr 27, 2022 2:53 pm

Albert Hofmann wrote:(Note also that any possible password/md5 problem would have been irrelevant in my tests because I just used "trust" for my LAN in the pg_hba.conf file, so no password was needed)

Just an afterthought:
Resolve may "insist on a pw method". The pw parameters may be hardcoded.
There may be no "try trust first" clause.
Thats not conclusive either, though, cause the pgclient could be content with the trust and dismiss the parameters silently, giving back ok.
Dunno. Just a vague feeling.
Offline

Albert Hofmann

  • Posts: 70
  • Joined: Wed Feb 24, 2016 10:01 am

Re: Recommended PostgreSQL version

PostWed Apr 27, 2022 4:47 pm

labor4 wrote:Just an afterthought:
Resolve may "insist on a pw method". The pw parameters may be hardcoded.


Well, no. The connection works fine, and Resolve creates the database and all the tables. It crashes only after all that. And anyway, the Postgres logs would show rejected connection attempts, which they don't in this case.
Offline

Gordonjcp

  • Posts: 172
  • Joined: Thu Apr 14, 2022 11:27 am
  • Real Name: Gordon JC Pearce

Re: Recommended PostgreSQL version

PostSun May 01, 2022 11:55 am

Albert Hofmann wrote:So, if your PostgreSQL server is running Ubuntu 20.04, you must use Postgres v. 9.6. It can be installed from the Postgres repositories.


Don't run Postgres on the server directly, run it in a Docker container. That way you can choose which version and OS it works on, without messing around potentially destructively with installing and uninstalling non-official packages.

Trying to cope with multiple versions of anything like that without containers will make for sad times eventually.
Offline

labor4

  • Posts: 18
  • Joined: Sun Feb 16, 2020 4:25 pm
  • Real Name: Manuel Weber

Re: Recommended PostgreSQL version

PostSun May 01, 2022 3:09 pm

Gordonjcp wrote:Don't run Postgres on the server directly, run it in a Docker container. That way you can choose which version and OS it works on, without messing around potentially destructively with installing and uninstalling non-official packages.

Trying to cope with multiple versions of anything like that without containers will make for sad times eventually.


Hi
Fair point.
I think your solution is good regarding a test setup, for my understanding.

But I myself am hesitant on DB containers in production.
I consider my lack of knowledge a problem if I begin to run DBs in containers, because I know too little on the accidents when reconstructing a persistent DB container, especially over time.

In theory, if I wanted to argue on the "bare multi PG" side, that you warned from, I would rename any default config path (ie /etc/posgres to /etc/posgresV14), data path, ports, right after installation, also parse out the hidden defaults, and make it run again after these hard changes, and so learn more about the coordinates of PG, to be sure all is separated.
Code: Select all
lsof
is also a helper to cross check.

However, my preference over that is a VM, snapshots, and a copy of the machine, making an IP based distinction beginning at Resolve.
Offline

Albert Hofmann

  • Posts: 70
  • Joined: Wed Feb 24, 2016 10:01 am

Re: Recommended PostgreSQL version

PostSun May 01, 2022 4:06 pm

That's all a matter of personal choice.
Personally, I prefer avoiding the added complexity of containers. And I feel there is nothing "non-official" about the official .deb packages provided by Postgres.

Also, I would advise not renaming the /etc/postgresql directory. If you have several postgres versions in the same machine, their configuration will automatically be under separate directories already:

Code: Select all
# tree /etc/postgresql
/etc/postgresql
├── 11
│   └── main
│       ├── conf.d
│       ├── environment
│       ├── pg_ctl.conf
│       ├── pg_hba.conf
│       ├── pg_ident.conf
│       ├── postgresql.conf
│       └── start.conf
└── 9.6
    └── main
        ├── environment
        ├── pg_ctl.conf
        ├── pg_hba.conf
        ├── pg_ident.conf
        ├── postgresql.conf
        └── start.conf


And of course, it does the same for it's data directories, which are also clearly separated.

So in short, unless you really know exactly what you are doing, leave the OS and Postgres manage all this. They have been doing it right for as long as I can remember (almost 2 decades!).
Offline

Gordonjcp

  • Posts: 172
  • Joined: Thu Apr 14, 2022 11:27 am
  • Real Name: Gordon JC Pearce

Re: Recommended PostgreSQL version

PostSun May 01, 2022 10:15 pm

> They have been doing it right for as long as I can remember (almost 2 decades!).

Having done Unix-y stuff for rather more than two decades, I'd say that having a server you can destroy and recreate in a single command is probably better than hoping that the vendor packages don't step all over each other.

If you're mad enough you can even run Resolve in a container - I do, because I don't want to nuke 17.4.6 but I also want to play with 18b1, so this lets me choose.

Out of interest, is the Project Server any more than just a Postgres database with a cool user-friendly GUI?
Offline

roadrunner

  • Posts: 33
  • Joined: Wed Jul 29, 2020 1:48 am
  • Real Name: Nathan Tyler

Re: Recommended PostgreSQL version

PostTue May 10, 2022 1:33 am

Just a note for what it's worth, if you're running Docker it will still let you use version 9, just use "9" as the tag instead of the default "latest" tag. Although the docs don't mention earlier versions than 11, the container images are still there in the repository.

After a few false starts with later versions I've spun up a container with version 9 and it's all working happily.

This is on a TrueNAS Scale server which is running on Debian.
System 1: Dell Precision 7810, Dual Xeon 2620, 72GB RAM, GeForce 1080ti 11GB, Win10 pro, Resolve Studio 17.4.
System 2: Custom build Intel i7-12700K, 64GB RAM, GeForce 1080ti 11GB, Ubuntu 22.04, Resolve Studio 17.4.
Offline
User avatar

Olivier MATHIEU

  • Posts: 865
  • Joined: Thu Aug 04, 2016 1:55 pm
  • Location: Paris/Grenoble, FRANCE

Re: Recommended PostgreSQL version

PostTue May 10, 2022 7:08 am

Gordonjcp wrote:Out of interest, is the Project Server any more than just a Postgres database with a cool user-friendly GUI?

Why "any more". for me it's "still" :) isn't it ?
Resolve Studio 18.6.x & Fusion Studio 18.6.x | MacOS 13.6.x | GUI : 3840 x 2160 | Ntw : 10Gb/s
MacbookPro M2 Max
Offline

lpaolini

  • Posts: 5
  • Joined: Mon Mar 07, 2022 4:05 pm
  • Real Name: Luca Paolini

Re: Recommended PostgreSQL version

PostFri Sep 08, 2023 8:12 am

I'm using Resolve 18.5 with PostgreSQL 15.3 running on my QNAP TS-221 on Debian 12.1 "bookworm".
So far so good.

Return to DaVinci Resolve

Who is online

Users browsing this forum: BartReynaard, Bing [Bot], NormDave, panos_mts, peeceful, Shadowplay and 230 guests