Resolve 17 BtException: error: when creating new postgreSQL

Testing the Resolve 17 (non-Studio) with postgreSQL.

I'm able to connect to the server, the database is created, but before completing the process I'm getting the following error:

BtException: ERROR: syntax error at or near "="
LINE 1: UPDATE "SM_Project" SET =F8FFC26A553A WHERE = ff2e540a-f4b4...
(42601) QPSQL: Unable to create query

The application has recovered from the error. It is advisable to save the project and restart the application. Please mail the details of the error to Blackmagic Design, and contact Blackmagic Design Support if the error persists

You can see the error in SQL request above under "LINE 1" after "SET" (no column name) and after "WHERE" (no column name).

Any idea what the underlying cause might be?

Problem solved: Issue was apparently the postgres version: posgres v13.2 was apparently too new.
A number of posts suggest that postgres v9.5.4 was required.
That worked.
Also tested with v11 and so far that seems to be working fine as well.

Followup question: What is the most up-to-date version of postgres compatible with Resolve 17?

As far as I can remember it works with 12

I was having a similar issue and found it was because by default my new version of PostgreSQL didn't include the default postgres role (I'm using a QNAP NAS and a docker version of PostgreSQL, in which the default role is qnap_postgres).

I dug through the logs and found the actual issue:
[0x00003d7c] | DbCommon2 | WARN | 2021-06-24 12:45:17,934 | Failed to initialize database [REDACTED]: Failed to create baseline schema on database [REDACTED]: ERROR: role "postgres" does not exist

I added the role and it fixed the issue immediately.

Note, this is independent of the sign in username.

Followup question: What is the most up-to-date version of postgres compatible with Resolve 17?

I tested this today in DaVinci Resolve Studio 17.3 BUILD 14 (Linux), starting from the most recent version of PostgreSQL (under Arch Linux) and working backwards. If it failed, it failed with the issue from your OP.

☒ PostgreSQL 13.3
☒ PostgreSQL 12.7
☑ PostgreSQL 11.12