3 ms·
Rather than a query planner, an interesting approach would be to expose the more stable part of the internals with a new language and let people roll their own
by roenxi 6y ago
Rather than a query planner, an interesting approach would be to expose the more stable part of the internals with a new language and let people roll their own query plans. Then Postgres can be NoSQL too and we can all be happy.
I'm not hopeful that it would be technically feasible, but it isn't obvious that Postgres needs to only support SQL as an interface. The SQL language is so horrible I assume it is already translated it into some intermediate representation.
- snuxoll 6y ago> expose the more stable part of the internals with a new language and let people roll their own query plans. You’re basically talking about ISAM style access at this point. Even IBM started discouraging that on IBM i and is pushing developers to use embedded SQL instead.
- assface 6y ago> Rather than a query planner, an interesting approach would be to expose the more stable part of the internals with a new language and let people roll their own query plans. Those that are ignorant of history are doomed to repeat it. Go read Stonebraker's "What Goes Around Comes Around" https://15721.courses.cs.cmu.edu/spring2020/papers/01-intro/whatgoesaround-stonebraker.pdf https://15721.courses.cs.cmu.edu/spring2020/papers/01-intro/...
- CaptainZapp 6y agoThank you! This paper (only started on it) looks fantastically interesting. And yes, I'm old enough to actually have worked on hierarchical databases.