3 ms·

Makes sense, thanks. I thought maybe this was a smaller change where you just used a different layout/representation of the tree that allowed faster, more cache

Makes sense, thanks. I thought maybe this was a smaller change where you just used a different layout/representation of the tree that allowed faster, more cache-friendly evaluation, but you've actually gone much further with this VM, which is fascinating given that it opens up the possibility of JITing queries. My day job involves working on a query engine that faces some of the same design challenges, so I find this stuff very interesting.

anarazel 8y ago
> but you've actually gone much further with this VM, which is fascinating given that it opens up the possibility of JITing queries. That's why I did it, and why that's the first part in PG 11 that got JITed ;) > My day job involves working on a query engine that faces some of the same design challenges, so I find this stuff very interesting. FWIW, part of the design decisions I made for this stuff in PG were made to a significant part because it had to be adaptable incrementally without breaking too many idiosyncrasies (although there were some, in another commit, around multiple set-returning-functions in the SELECT list). I'd definitely do some things differently if I were to design more on a green field.