Mike Stonebraker

And there's a huge programming community, all kinds of data type implementations.

It's free.

And you can find Postgres talent easily and get going.

And so I think it's a great choice for lowest common denominator.

And until you're trying to do...

a million transactions a second, it works just fine.

Until you're trying to support a petabyte data warehouse, I say at the low end, it's absolutely the right.

One size fits all at the low end, it's Postgres.

At the high end, that's just not true.

Probably, but I think the big challenge is that GPUs are...

You know, SIMD, you know, single instruction, multi-data.

And that's the anathema of indexing.

And so whenever indexing is the right answer, they're probably not a good idea.

And I think also you've got to architect them so that the bandwidth from storage is not the bottleneck.

And so if they're an add-on to the CPU, as often as not the bus connecting it to the GPU to the CPU is a bottleneck.

So let's say I'm looking for Ryan's salary and I have a B-tree.

So you go to the root of the B-tree.

You find the divider that has both sides of Ryan.

You follow the pointer.

That's a memory access for sure.