You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 20, 2022. It is now read-only.
After upgrade from version 5.21 to 5.30 or 5.31 I have an error in db container: ERROR: canceling statement due to user request STATEMENT: SELECT p.*, (SELECT COUNT(Posts.Id) FROM Posts WHERE Posts.RootId = (CASE WHEN p.RootId = '' THEN p.Id ELSE p.RootId END) AND Posts.DeleteAt = 0) AS ReplyCount FROM Posts p WHERE (CreateAt < (SELECT CreateAt FROM Posts WHERE Id = $1) AND ChannelId = $2 AND DeleteAt = $3) ORDER BY ChannelId, DeleteAt, CreateAt DESC LIMIT 30 OFFSET 0
And history doesn't load with error 500 in the browser console. Our Database size 11 GB. Also, I have changed the QueryTimeout value in config.json from 30 to 300 seconds according to the documentation here. After that history was loaded in 2 minutes. Before upgrade history loaded faster (I didn't change the default QueryTimeout parameter).
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
After upgrade from version 5.21 to 5.30 or 5.31 I have an error in db container:
ERROR: canceling statement due to user request
STATEMENT: SELECT p.*, (SELECT COUNT(Posts.Id) FROM Posts WHERE Posts.RootId = (CASE WHEN p.RootId = '' THEN p.Id ELSE p.RootId END) AND Posts.DeleteAt = 0) AS ReplyCount FROM Posts p WHERE (CreateAt < (SELECT CreateAt FROM Posts WHERE Id = $1) AND ChannelId = $2 AND DeleteAt = $3) ORDER BY ChannelId, DeleteAt, CreateAt DESC LIMIT 30 OFFSET 0
And history doesn't load with error 500 in the browser console. Our Database size 11 GB. Also, I have changed the QueryTimeout value in config.json from 30 to 300 seconds according to the documentation here. After that history was loaded in 2 minutes. Before upgrade history loaded faster (I didn't change the default QueryTimeout parameter).
The text was updated successfully, but these errors were encountered: