-
Notifications
You must be signed in to change notification settings - Fork 409
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Persistent cache #6589
Persistent cache #6589
Conversation
Queries after DDL in a transaction have been running without cache for some time, dropping the dead code for now; maybe we will add it back in the future properly.
During a query compilation, if the schema is changed, the server was caching the compiled query under a wrong dbver, causing future queries to fail. See the test for issue reproduction.
d184c52
to
f617fe1
Compare
f617fe1
to
2e2341a
Compare
22e1993
to
2936ae1
Compare
@@ -535,7 +535,13 @@ cdef class DatabaseConnectionView: | |||
raise errors.InternalServerError( | |||
'no need to serialize state while in transaction') | |||
|
|||
ver = self._db.schema_version | |||
ver = hash( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Will ver
ever end up in Postgres or in another Python process? hash()
as you know is randomized
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Negative. In Postgres, it's in the state temporary table and never used.
15a04d4
to
83f17ec
Compare
83f17ec
to
e3545ca
Compare
f6175f0
to
064d99f
Compare
Close in favor of #6881 and many others. |
Closes #6349
Add LRUMapping.gc()we can usestmt_cache.pyx
dbver
with the non-local schema version