Yeah, my db file is up to 81M now so I’ll have to setup a similar maintenance cron job. Thanks again for the workaround, hopefully it won’t be a longstanding issue.
Still have this issue in 1.19.3.2764!!!
I have been fighting like crazy with this for weeks now…
Can someone please ping someone relevant in the plex team to take a look at this?!?
I will try the clean statistics tip.
Can other users with this problem confirm on having a ubiquity controller within their networks? I have one, but unlike john here, my L2 discoverability was already turned off.
I get roudabout 1Million new entries into statistics_media per week. Someone at plex has to fix that bug quickly!
1 Like
I have a ubiquity controller in my network. L2 turned off.
I haven’t seen “held transaction for too long” since I deleted statistics from DB.
Was the “Held transaction for too long” issue identified as a bug?
I have my PMS database stored on an external 1TB USB3 SSD so wondering if its too slow or if this is an actual bug.
Held transaction for too long (../Library/MetadataItem.cpp:3590): 1.060000 seconds
LOW QUERY: It took 490.000000 ms to retrieve 50 items.
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
