Postgres 19 is late, and it's AI's fault
0 comments · databases, practices
- Comments20
0 comments · databases, practices
Story details from Lobsters ↗ · linked article on rhaas.blogspot.com.
Postgres 19 is late, and it's AI's fault was first seen on Lobsters · Hottest on Nov 2, 2026. Since then it has appeared in 80 checks on 2 different days. Its best position was #2 of 25, reached on Nov 2, 13:21 UTC. It dropped off the list after Nov 3, 19:51 UTC. The same link also trended on Hacker News, which raises its cross-platform score.
Position on Lobsters · Hottest at every check (lower is better).
Best rank per day (UTC).
Platform metric as reported by Lobsters.
| List | Best | Days | Checks | Last seen |
|---|---|---|---|---|
| Lobsters · Hottest | #2 | 2 | 80 | |
| YHacker News · Front page Postgres 19 is late, and it's AI's fault | same link | |||
A few top-level comments from Lobsters, shortened. Read the full thread on Lobsters.
So I read this title and thought "ah great, yet another article complaining about vibecoded features and their slop". But then I remembered reading some other article about PostgreSQL 19 in the last few weeks and how it claimed that none of its features had been written with the help of LLMs. Which made me curious to…
As much as I dislike LLMs, this seems… fine? We’re living in the age of slop where velocity is prioritized over quality. Going the other direction is good.
Archived daily, weekly and monthly lists that include this entry.
Not at the moment. It was last on the list on Nov 3, 19:51 UTC, after 2 days of trending.
#2 on Lobsters · Hottest, on Nov 2, 13:21 UTC. Trendoday checks this list every 30 minutes.
It was first seen on Nov 2, 2026 and has been on the list on 2 days (80 checks) since.