sql: move temp tables out of preview

cockroachdb / cockroach

CockroachDB - the open source, cloud-native distributed SQL database.

https://www.cockroachlabs.com

Other

29.51k stars 3.7k forks source link

sql: move temp tables out of preview #46260

Open otan opened 4 years ago

otan commented 4 years ago

Currently, temp tables (/views/sequences) are experimental. This issues is be a "master issue" of things remaining to do before moving it off experimental.

Things to do:

[x] performance benchmarks (https://github.com/cockroachdb/cockroach/issues/46213)
[ ] complete schema resolution caching which prevents slowdowns with new schemas in force
[ ] move descriptors from gossiping all descriptors to only gossiping deltas

Enhancements

[ ] potentially be in-memory by default
[ ] smarts about locality in which they were created

(feel free to edit, I couldn't find any more for the time being)

Jira issue: CRDB-5098

gz#22057

andreimatei commented 4 years ago

I think there were more problems than listed above with the temp tables. I think we'd want an in-memory implementation for them by default, and some smarts about the locality in which they're created. There was a lot of discussion on the RFC; have you found those threads?

otan commented 4 years ago

Nope, this (so far) isn't a definitive list (I just wanted to create the issue). Feel free to edit (or lead me to where to find them)!

jpollard-cs commented 1 year ago

Hello just curious if there's any update on this? Appreciating that this is likely more complex in the Cockroach case for various reasons I can see this being a potential question for our internal customers deciding between Cockroach and Aurora given Aurora uses local storage for temporary tables which can significantly improve read performance for some workloads.

ajwerner commented 1 year ago

The history here is that temp tables are used extensively in ORM test suites. We really wanted that coverage, so we implemented temp table support to be correct, but not efficient. Internally, they use real tables and all the overhead which comes with them. There is no immediate plan to implement performant temp tables.