Injecting a Chess Engine into Amazon Redshift
3 comments · assembly, c, databases
- Comments3
3 comments · assembly, c, databases
Story details from Lobsters ↗ · linked article on michaelburge.us.
Injecting a Chess Engine into Amazon Redshift was first seen on Lobsters · Hottest on Oct 31, 2026. Since then it has appeared in 1 check on 1 different day. Its best position was #5 of 25, reached on Oct 31, 05:21 UTC. It dropped off the list after Oct 31, 05:21 UTC.
Position on Lobsters · Hottest at every check (lower is better).
Best rank per day (UTC).
A few top-level comments from Lobsters, shortened. Read the full thread on Lobsters.
> If you’d like to try it on your live production database Good one :-)
He appears to be exploiting the fact that the extension to allow embedded python functions in postgres (and redshift) is unsafe, and able to execute arbitrary code. Of course, you could also simply write the chess engine in python (rather than in C++ injected into python), or whatever extension language is available.…
Is this something Amazon could easily patch out of their query compiler? What's the generally accepted way of optimizing CPU-bound queries without injecting assembly code- would it be splitting a query into multiple ones: Query pt1 -> do some CPU -> Query pt2?
Not at the moment. It was last on the list on Oct 31, 05:21 UTC, after 1 day of trending.
#5 on Lobsters · Hottest, on Oct 31, 05:21 UTC. Trendoday checks this list every 30 minutes.
It was first seen on Oct 31, 2026 and has been on the list on 1 day (1 check) since.