Copy Db from local to Postgres fails or crashes Resolve 17.1

Hello

Copy or importing a local database to Postgres crashes Resolve or fails with a message.

On a copy/paste from the local to Postgres Db Resolve shows a dialog "Unable to Import Project". Doing an Export / Import crashes Resolve. Both happen around 96/98%

Looking at a debug log to see if I could find anything I see a SQL statement with an unterminated quoted string.
Here is a snapshot of the log for DbCommon2 truncated at each line:
INSERT INTO "ListMgt::LmVersion" ("ListMgt::LmVersionTable_id", "ListMgt::L
Sm2SequenceContainer -- ERROR: unterminated quoted string at or near "'\x4
Rollback is called within nested transaction, postpone rollback action till the last
UPDATE "Sm2SequenceContainer" SET "Sm2Sequence_id"='5cc2307a-050f-48
Failed to save Project's mediaPool.
SM_Project -- SaveMediaPoolOrLockableBlobMap FAILED --

I successfully copy pasted a simple almost empty project with 4 stills and fixed node structures from the local database to Postgres and can create projects there which I think rules out the Postgres Db or NAS. Some of my media is offline because of Big Sur and a PegasusR2 drive but I unlinked those files and that did not help.

Thanks.

------
OSX Big Sur 11.2.2
Resolve 17.1 Build 24.
Postgres 9.5.4 on QNAP NAS.

The Resolve 17.1.1 update of March 31 mentions it "Addressed an issue with restoring older database backups."

My issue is still happening with this update when importing to the PostGres DB. Just as before, Resolve crashes on import at about 90%. The logs show the same issue with unterminated quoted string (in a blob).

I've removed all the instances that I can find relating to this message. It appears to be a node grade version but I've removed all I can find including in the Stills but it still shows. I don't understand how?

I updated Resolve; restarted the computer, saved Global Preferences (to make sure the configs are updated). I also exported and imported the project in the local, File version DB.

Not sure if the fix in this version was in reference to this bug so posting again.

Thanks
Eric
Last I heard was this:

I see the same behavior here. That drp imports into a Disk database with no issue, but fails importing into a PostgreSQL database.

I've asked the Resolve dev team to have a look, and they've repo'd and logged the issue as a bug, and will look into it further.

Ticket Details
Ticket ID: ZMC-970-87785
Department: Support
Type: Issue
Status: Open
Priority: Normal

Actually this issue is saving a project.
With version 17 is the ability to export a single timeline.
In this case I exported the timeline and successfully imported it into a new project.
Only when I tried to save the project did Resolve crash.
As before this is from a disk based project to a Postgres version. I have had no problems moving other projects from disk based to the PG instance.