Just found at least two books on topics of my interest and there are several more that I think I will read in the future. This is a good resource. Thank you!
" also, it's a bit weird to write a critique like yours for the launch of a new platform"
I think this is a fair critique because the release announcement states the product should address the symptom that "nearly half of us never make video calls on mobile". If you believe the underlying problem is that lack of eye contact makes video calling low-value to many people this is not a viable solution.
Postgres has an extensible type system so Radix sort isn't really suitable, it really needs a comparison sort.
For SSE/MMX/AVX/etc or GPU sorts it would have to use integer or floating point surrogate keys. It would probably be the same abbreviated keys mentioned in the last few slides. That could be a radix sort but generally I think bitonic sort is preferred.
> Postgres has an extensible type system so Radix sort isn't really suitable, it really needs a comparison sort.
That's not quite true. It supports string tries, for example (using SP-GIST). Such operations just have to be built for specific types. I think it would be more accurate to say that (AFAICT) Postgres doesn't currently have any way to extend the optimizer with custom plans (though it's been a very popular feature suggestion).
> I think it would be more accurate to say that (AFAICT) Postgres doesn't currently have any way to extend the optimizer with custom plans (though it's been a very popular feature suggestion).
