41–47 of 47 posts
I consulted at some Indian startups. Such bad queries were written which were costing them so much compute I just rewrote all queries with claude code and next day and compute decreased to 1/5th.
I consulted at some Indian startups. Such bad queries were written which were costing them so much compute I just rewrote all queries with claude code and next day and compute decreased to 1/5th.
Kind of a weird flex - you're basically saying that you aren't any better than the Indian teams at writing efficient queries or optimizing existing ones, the only talent you've demonstrated is ability to ask Claude Code. It's like you are announcing your own obsolescence.
Earlier quoted context omitted.
I think your assumption about inlining is essentially correct. As far as I know postgres was the last major rdbms to have an optimiser fence around CTEs.
I concur, “the Germans” have created an algorithm that completely “see through” subqueries/CTEs when planning a query. The way the query is written has no bearing on the execution.
These days I often write queries like this (especially when doing exploratory ad hoc queries, but also in apps) even when it's not necessary to use a CTE:
WITH
a AS (
SELECT ... FROM ... WHERE ... etc.
)
SELECT * FROM a
This has a bunch of nice benefits. For example, it allows me to add steps incrementally, and to "comment out" a step I can simply change the next step's input to read from the preceding step. Each step can be read and understood in isolation.
I work a lot with Postgres, ClickHouse, and SQLite, and generally find that the database inlines and optimizes CTEs, and challenges mostly concern performance traps (like IN or EXISTS) that allly to non-CTE situations as well.
Earlier quoted context omitted.
As someone who is not much of a sports person, now I was wondering what CTE means in sports. Seems to be this: > Chronic traumatic encephalopathy (CTE) is a progressive neurodegenerative disease […] > Evidence indicates that repetitive concussive and subconcussive blows to the head cause CTE. In particular, it is associated with contact sports such as boxing, American football, Australian rules football, wrestling, m…
Yep, that's it. The NFL in the US has famously gone to great lengths to downplay the impact of CTE on current and retired players. And there have been several famous players who literally lost their minds as they aged, and we now know that was due to CTE. Something like 90% of ex-NFLers have it. The number is still really bad for collegiate players. And even high school players are at risk. It was to the point that W…
Earlier quoted context omitted.
I concur, “the Germans” have created an algorithm that completely “see through” subqueries/CTEs when planning a query. The way the query is written has no bearing on the execution.
By the Germans, as you referring to Thomas Neumann's database group at TMU, Munich?
Earlier quoted context omitted.
Your comment could have been more helpful without the first sentence. SAME content, same correction, less superiority: "CTE is an overloaded term, in this article ......" This is a valuable comment, don't ruin it with sarcasm and rudeness.
> Your comment could have been more helpful without the first sentence. no it wouldn't the whole point is to critique the post
> Use the term, never define the term, classic.
Communicate the same thing in a way you'd do to someone's face:
> This article doesn't define the term "CTE".
Or even more directly, still not rude:
> I wish the article had defined its terms! "CTE" stands for "Common Table Expressions..."