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.

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

Avoid pickling schemas on _every_ DDL statement when restoring a dump #6362

Merged
merged 1 commit into from Oct 26, 2023

Conversation

elprans
Copy link
Member

@elprans elprans commented Oct 26, 2023

restore() doesn't care about anything other than compiled SQL or
config ops, so pickling and returning the schema with every DDL query
unit is wasteful, and, if the schema is large, quite slow.

`restore()` doesn't care about anything other than compiled SQL or
config ops, so pickling and returning the schema with every DDL query
unit is wasteful, and, if the schema is large, quite slow.
@elprans elprans merged commit c7e0a06 into master Oct 26, 2023
22 checks passed
@elprans elprans deleted the speedup-restore branch October 26, 2023 05:45
aljazerzen pushed a commit that referenced this pull request Oct 26, 2023
…#6362)

`restore()` doesn't care about anything other than compiled SQL or
config ops, so pickling and returning the schema with every DDL query
unit is wasteful, and, if the schema is large, quite slow.
msullivan pushed a commit that referenced this pull request Oct 27, 2023
…#6362)

`restore()` doesn't care about anything other than compiled SQL or
config ops, so pickling and returning the schema with every DDL query
unit is wasteful, and, if the schema is large, quite slow.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants