Good to see some movement on plan hints in postgres, but I can't get behind the ergonomics of stashing plan advice via query ID. Comment-based hints can be declared in the application, which is typically when you will want to update the hints when modifying the query. It's just a much simpler workflow and one which has a lot of precedence in other DBMSs.
Quality content stopped being profitable well before ChatGPT. Quantity beat quality as a content strategy flooding the search page with high-level obvious “how-tos” and “best vacuum cleaner” slop. This destroyed the consumer search experience. Current models have plenty of rich historical data and are good at synthesizing quality responses with the right queries. Now the risk is that AI will be starved of recent quality information to pull from. Hopefully the pendulum swings back around to make quality information profitable again…
Really exciting to see the progress on this project! I'm not sure I understand the update "we are in production." Is this referencing a particular release or a more general statement about adoption?
This is a really interesting project I found which could be used to detect plan flips and introspect why the Postgres optimizer chose a certain path. Normally that is opaque to the user.
It would be awesome if this were to make it in core. Jelte did a bunch of work to improve query protocol changes. Having Postgres accept Otel trace propagation would be a gamechanger for debugging the clients and DB together. Especially since ~80%+ of DB related issues I see come down to some sort of long running open transaction which Postgres knows nothing about server-side.
> Every metric I can find online says that MySQL/MariaDB is more popular than PostgreSQL
What are those metrics? If you're talking about things like db-engines rankings, those are heavily skewed by non-production workloads. For example, MySQL still being the database for Wordpress will forever have a high number of installations and developers using and asking StackOverflow questions. But when a new company or established company is deciding which new database to use for their custom application, MySQL is seldom in the running like it was 8-10 years ago.
Also somewhat surprised. DuckDB traction is impressive and on par with vector databases in their early phases. I think there's a good chance it will earn an honorable mention next year if adoption holds and becomes more mainstream. But my impression is that it's still early in its adoption curve where only those "in the know" are using it as a niche tool. It also still has some quirks and foot-guns that need moderately knowledgeable systems people to operate (e.g. it will happily OOM your DB)