This type of story about management getting rid of the old guard is so common and typical, it remains one of the most frustrating aspects of this industry.

In the “enterprise scene”, this sort of purge strategy is likely linked to a big percentage of money wasted and sometimes total failure.

Why do managers keep making this mistake? “Legacy” is only a bad word in IT. :-(

On the other hand, it is not uncommon for the exiled old guard to form new companies, teams, products and realize their vision under new management.

It is not like their knowledge and experience gets literally purged.

Because their KPIs are all about making a impact.

Apple doesn't use KPIs for performance reviews.

(Also, eg Ali Ozer is still there.)

Tomato tomato, employees do have to meet performance goals of some sort.

Thank you for this.

(I think HN should consider creating TLDR type of comments for upvoting separately from commentary. @Dan incentivise with different karma credits?)

I read "man months".

Off-topic: TIL wal2 mode in the works. Wow. That's a no-brainer feature, IMHO.

Is the 300x performance boost attributable to the threading model vs process model?

Was the code for the threading model written by hand or was it translated from the WIP threading model the human PG team is busy with as part of the 2028 roadmap?

I'd like to know on what machine and on what testbench the supposed 300x boost is achieved so that we can independently verify it. My assembler-written fork of postgres is achieving 600x boost on SELECT 1;

Chuckled at the anti-climactic sentence ending! lol

Unlikely. It goes further by also using the word "exploit".

If they needed permissions for conversion, they'd have made a specific mention of that and thereafter confirmed legal ownership.

TBH, I like that the word “exploit” is in there. It feels more honest and if it were not present!

Genuine question: how did you figure this was AI generated? (If that is what you meant.)

The quoted phrase is one of the hallmarks of LLM-isms. He is 100% correct

Nice.

Is if a one thread per request model?

Does it support async await type of architecture?

By definition, a FK has to reference a PK in the “parent”.

Not quite. It can reference any combination of columns with a unique index (of with the PK is by definition).