124 Followers
127 Following
358 Posts

@hailey aaah. my purpose was to not change Postgres itself at all and only use the public functions.

oh wow, rewriting the code automatically to make global variables into function calls is super neat!

@joeldrapper I'm actually missing a broader community where more people share maintenance of projects/gems. I feel that more people could do point-releases (and bumping dependencies) while there still being a main owner of a gem.
@hailey hopefully you're using a more public API than I was trying. I was trying to make it not use _anything_ on disk. I started poking into the "relation cache" and then I got kinda stuck.

@hailey aaah. I was trying to tweak the internals so that tables were not stored on disk, but I could use parts of the query engine. it was *complicated*.

but if you're just using the stock Postgres features then I guess librarizing it will be okay!

@hailey what are you doing next?

I recently tried to use Postgres as a library and unfortunately quickly discovered that there’s a lot of global state and global functions :/

@postmodern the ironic thing here is that this binary tree is the *simple* part. next up is a more compact, pointer-free, representation of the same data, but I first need the tree to know the structure to encode.
so I opted for some unsafe code and raw pointers. I have no clue whether this is undefined behavior or not, but at least the tests pass.
implementing a binary tree with parent pointers and rotation in Rust => not recommended!!
@Zolytech huge fan of Roda and Sequel!
@jsrn IMO, it’s a lot easier to understand the output when you have a concrete, real-life query which performs terribly. I think I’ve only looked at EXPLAIN after something was slow. (or before deploying something which I suspected would be slow.)