- Notifications
You must be signed in to change notification settings - Fork27
Refactoring#7
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
…ing of pg_query_state
d2655af to56817adCompareREADME.md Outdated
| ##Overview | ||
| Eachcomplex query statement (SELECT/INSERT/UPDATE/DELETE) after optimization/planning stage is translated into plan tree wich is kind of imperative representation of declarative SQL query. EXPLAIN ANALYZE request allows to demonstrate execution statistics gathered from each node of plan tree (full time of execution, number rows emitted to upper nodes, etc). But this statistics is collected after execution of query. This module allows to show actual statistics of query running on external backend. At that, format of resulting output is almost identical to ordinal EXPLAIN ANALYZE. Thus users are able to track of query execution in progress. | ||
| Eachnonutility query statement (SELECT/INSERT/UPDATE/DELETE) after optimization/planning stage is translated into plan tree wich is kind of imperative representation of declarative SQL query. EXPLAIN ANALYZE request allows to demonstrate execution statistics gathered from each node of plan tree (full time of execution, number rows emitted to upper nodes, etc). But this statistics is collected after execution of query. This module allows to show actual statistics of query running on external backend. At that, format of resulting output is almost identical to ordinal EXPLAIN ANALYZE. Thus users are able to track of query execution in progress. |
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.
wich надо поправить
| , plantext | ||
| , leader_pidinteger) | ||
| AS'MODULE_PATHNAME' | ||
| LANGUAGE C STRICT VOLATILE; |
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.
если меняется sql, значит пора менять версию, надо этот файл переименовать во что то нейтральное и генерировать файл pg_query_state--1.1.sql во время сборки (смотри DATA_built переменную в Makefile), плюс добавить миграционный файл 1.0-1.1 который удаляет эти функции при миграции с 1.0 до 1.1.
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.
Сделано
Версии 9.6 и 10 объединены в одну ветку. Тесты портированы из версии 9.5.