17
PostgreSQL in-database durable execution
(github.com)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 05 Jun 2026
17 points (94.7% liked)
Programming
27173 readers
322 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 3 years ago
MODERATORS
Ah, so we're trying to embrace, extend and extinguish Postgres now are we Microsoft? Good luck.
Am I missing something here? It's an open source Postgres extension with a permissive license. Azure has had hosted Postgres databases for years, as have all the other major cloud providers. I'd be concerned if they were ecosystem locking the extension, but that doesn't appear to be the case.
The motivation for this extension, hilariously, is likely to run AI. With how long requests can take due to inference, durable execution is useful to avoid losing data mid-request and needing to restart the whole thing. This seems useful outside of that though, for other kinds of long-running requests.
All you're missing is that I loathe microslop and will no longer extend them even a nanometer of goodwill. They deserve nothing but mistrust. They have burned all possible bridges. I'm entirely done with them, forever.
I don't like them either, but I do think it's important to differentiate things that companies (and people) do that benefit others from things that harm them. This contribution to open source stands in contrast to all the shit they've done recently and over time with Windows, AI, and so on.
It's a bait and switch, and you're taking the bait. Microsoft does not do anything that benefits others, they only do things that benefit themselves, and if you think they're benefiting you, that's the trap, and you can sniff around it all you like until you're convinced it's safe, eventually they're going to catch you, you're not smarter than the multi-billion-dollar trapper who has already caught and killed and stripped the pelts off so many others. You will be no different.
Well I don't use this extension, no do I plan to. That aside, anyone can fork this repo and maintain it themselves. It feels like a stretch to say this isn't a benefit to society when anyone can use it and fork it without limitations or payment.
The rest of what you're saying is inapplicable here, but is applicable to other stuff they do. EEE is usually when they buy a product or service (Skype, for example) and kill it off (which was possible because Skype was a closed source service). You can't really EEE an open source project. Even vscode has popular forks, and there's nothing MS can do to stop them (outside frivilous lawsuits I guess).
I see you're younger than some of us. That's okay.
EEE was explicitly coined by M$ in the 90s and early 2000s, targeted at open source software.
Embrace the (opensource) standard. Become the gold standard of it.
Extend it with proprietary additions. Leverage them to make your competition inferior, and patent lock them out of the functionality needed for 20 years.
Extinguish the rest of the field - no longer support anything outside your special slop. Congratulations, you used free software to build a proprietary walled garden that competes with it.