MVCC

Yeah,

so in my case, I think you're touching the topic where people have pain, true pain.

And it's like we have had the deboss recently and also the topic of implementing cues and postgres, it's also like painful.

But still, these topics, they flame huge discussions because there is real pain people experience.

Right.

And first of all, I liked the depth and visualization piece.

Obviously you use the eye for it.

This is great.

I like it a lot.

And comparing to others, I think the main thing which is hanging in the air is that Postgres needs multiple different engines, and there is a demand for it.

Because this approach that we have right now, the only approach, it has issues in some workloads, and it's inevitable to hit those issues,

right? And you just said it in some workloads.

We can't be comparing apples and oranges.

And I think actually you summarize the goal that I had.

I wanted only to point out there is no free lunch.

You have to know what you, and this is what I'm doing with a boring SQL.

You need to know what you are optimizing for.

And actually Nick, your queue implementation is one that actually started the discussion because Now I have to admit I was in a I don't mind using Postgres.

I work with them, but you did actually the turnover.

You changed the bloat situations into something that doesn't regress.

Just in

case it was not me, I just repackaged Skype's 20-year-old implementation.

I just repackaged it so you can use it everywhere.

It's a very old thing.

Just modernized, that's it.