-
Notifications
You must be signed in to change notification settings - Fork 3.8k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
57644: sql,colexec: preliminary changes for wrapping LocalPlanNode r=yuzefovich a=yuzefovich **sql: order the output of some SHOW queries deterministically** This commit modifies several internal queries for SHOW commands to make the ordering of the output deterministic. The following had been augmented: - SHOW PARTITIONS - SHOW CREATE - SHOW INDEXES - SHOW COLUMNS (this also had an addition of ORDER BY clause of array_agg that computes the set of indexes) - SHOW CONSTRAINTS. Additionally, several logic tests were adjusted to use `rowsort` directive when ORDER BY isn't specified in the query as well as some EXPLAIN tests were moved into the execbuilder ones. This work was prompted by the fact that the vectorized engine produces the output for those queries with a different order (which is valid given omitted ORDER BY clauses before) than the row-by-row engine. Release note (sql change): Several SHOW commands have been adjusted to enforce a particular ordering of the output rows. **colexec: use datum-backed type for Oids** Previously, we would use `Int64` canonical type family to represents Oids. However, such conversion is lossful because we're losing some information (like semantic type and resolvable name), so if we were to do `columnarize -> materialize` conversion on an Oid, we wouldn't get the same thing back in the general case. To go around this issue this commit switches Oid type family to be handled by the datum-backed type. This will have some performance hit, but the queries with Oids aren't expected to process a lot of data, so that hit could be safely ignored. Release note: None Co-authored-by: Yahor Yuzefovich <[email protected]>
- Loading branch information
Showing
36 changed files
with
200 additions
and
305 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.