Conversation
There was a problem hiding this comment.
Which ones and how did they change?
There was a problem hiding this comment.
This needs to include the old and new property names.
|
|
@martint should this be mentioned in RNs 24a40be#diff-e0284816dc894bb27744c956e222c2ae? |
|
|
|
|
There was a problem hiding this comment.
Change the semantics of the ``analysis_time_ms`` column in the ``system.runtime.queries``
table. Previously, it was the time spent on query planning. Now, it is the time spent on
semantic analysis of the query. (:issue:`1084`)
There was a problem hiding this comment.
Add ``planning_time_ms `` column to the ``system.runtime.queries`` table that shows
the time spent on query planning. This is the same value that used to be in the
``analysis_time_ms`` column. (:issue:`1084`)
There was a problem hiding this comment.
@kokosing, I'm not sure I understand what this is about. Where are the details displayed?
There was a problem hiding this comment.
List the user visible effect of this, if any, otherwise remove it.
efda15e to
5ddef85
Compare
|
Updated. @electrum, any additional comments before I merge it? |
electrum
left a comment
There was a problem hiding this comment.
Couple of comments, otherwise looks good
There was a problem hiding this comment.
This needs to include the old and new property names.
There was a problem hiding this comment.
This is a duplicate of the above.
Which comment, @findepi's? I added the line he suggested below it. |
29c5d9b to
3b463fb
Compare
electrum
left a comment
There was a problem hiding this comment.
Can you rearrange the order of general so that all the adds are at the end?
There was a problem hiding this comment.
How about
Add session properties that allow overriding the query per-node memory limits
There was a problem hiding this comment.
How about
Add session properties that allow overriding the query per-node memory limits
Many entries need editing. The PostgreSQL items need to be replicated for MySQL, etc.
Closes #1238