-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
SQLite: too many SQL variables (federation) #7174
Comments
can you paste the complete stacktrace (ie, the bit you've omitted with |
|
That
... I guess it could be split in different queries. |
Will try to work around with an sqlite compiled with |
if you're hitting that limit, you probably need to switch to postgres anyway... |
No it's OK, SQLite3 is a proper database. |
proper database or not, emprically it is an order of magnitude slower than postgres and synapse only supports it for test purposes. See also #2917. |
I didn't know it wasn't fully supported. In terms of load I'm OK, synapse usage is unnoticeable on my server. Is there a way to migrate SQLite data to PG? |
@clokep I think that irrespective of the fact that people should be using postgres on production systems, we can and should fix whatever is causing this on sqlite. (It looks like we should break a single massive SELECT query up into separate queries; see https://www.sqlite.org/limits.html#max_variable_number). |
I think this was fixed by #7274 |
Description
Can't log in after upgrade to v1.12.0
During login, server logs say:
(may be another problem)
Version information
The text was updated successfully, but these errors were encountered: