Every story and comment from the Hacker News API, in a layout borrowed from 2001.
A comment on What's new in the Postgres 16 query planner (a.k.a. optimizer). Parent comment
SELECT foo.x, bar.y FROM foo WHERE bar.z > random() ORDER BY foo.x;
SELECT x FROM foo ORDER BY x; -- Meanwhile, concurrent updates are happening to foo, so re-running the query gets a different result set.
"We choose to do this thing and the others, not because they are easy, but because we ask 'how hard can it be?'"
There are no comments on this comment yet.
SELECT foo.x, bar.y FROM foo WHERE bar.z > random() ORDER BY foo.x;
SELECT x FROM foo ORDER BY x; -- Meanwhile, concurrent updates are happening to foo, so re-running the query gets a different result set.
"We choose to do this thing and the others, not because they are easy, but because we ask 'how hard can it be?'"