-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Database conversion to Postgres fails due to string literal with NUL characters #2187
Comments
I'm having exactly the same issue (with handle_search_table as in the traceback here) - wondering if there's some way I can delete the table's data, and regenerate it once it's loaded into postgres, seeing as it's a search index which should be able to be regenerated from other data? |
First I hit the #2287 issue, after applying the patch. I get this problem. I droped the database. Then try to migrate the database. But this issue stays. What can I do to solve this? |
Just to update this issue, it is still present with the latest v0.23.0 release candidates although it is now a slightly different line number. @erikjohnston @ara4n Any idea what I can do about this?
|
In order to help diagnose this, it might help if you could share logs of the failing command (possibly with |
Here is part of the log. I tried to run it and output the logs to a file but for some reason that didn't work so I copied this from the terminal scrollback. I'll try to run it again but let me know if this helps at all. I didn't see any private info in here but let me know if there could be. https://gist.github.com/aaronraimist/e4b312c8d8dd44fc03787eae659a1bd7 |
#2187 contains a report of a port failing due to nul characters somewhere in the search table. Let's try dropping the offending rows.
sorry, I missed the previous references to |
This definitely fixed the db port script. Using that patch, the script didn't give any error message and seems to have completed normally. I think my server is running off postgres now! I'll just leave this issue open to make sure that patch lands in the next release in case anyone else is having this problem. |
I've merged the patch so will close this now. |
I am attempting to convert my Synapse database from SQLite to Postgres. When running the port script I recieved the following error:
How can I go about debugging and fixing this?
The text was updated successfully, but these errors were encountered: