Skip to content
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.

Sign up for GitHub

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

Jump to bottom

sql: use optimizer for Export query #36756

Closed
RaduBerinde opened this issue Apr 11, 2019 · 1 comment
Closed

sql: use optimizer for Export query #36756

RaduBerinde opened this issue Apr 11, 2019 · 1 comment
Assignees
@RaduBerinde
Labels
A-sql-optimizer SQL logical planning and optimizations. C-enhancement Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)
Milestone
19.2

Comments

@RaduBerinde
Copy link
Member

The EXPORT statement contains a select query. Currently, this is planned through the HP. We need to switch this over to the optimizer (when the optimizer supports everything the HP does).

The planning of the select query happens through PlanHookState.Select. The fix should be as easy as rewiring that function; the rest of the export implementation doesn't need to change.
@RaduBerinde RaduBerinde added this to the 19.2 milestone Apr 11, 2019
@RaduBerinde RaduBerinde self-assigned this Apr 11, 2019
@awoods187 awoods187 mentioned this issue Apr 11, 2019
Closed
7 tasks
@awoods187 awoods187 added C-enhancement Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception) A-sql-optimizer SQL logical planning and optimizations. labels Apr 22, 2019
@RaduBerinde
Copy link
Member Author

This is a dup of #33469.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@RaduBerinde RaduBerinde

Labels
A-sql-optimizer SQL logical planning and optimizations. C-enhancement Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)
Projects
None yet
Milestone
19.2
Development

No branches or pull requests
2 participants
@RaduBerinde @awoods187