PostgreSQL

TIL

I had a PostgreSQL database query where block number was float instead of an integer. (This would not ever happen e.g. in JavaScript, but this time we were using the best programming language in the world. Python).

Instead of taking under-milliseconds the query took more than ten minutes.

I'm not sure if this is because the index match is only for integers, or if PostgreSQL is doing some other unusual behaviour. 

But this was damned hard to find.

Talks about crypto and coffee. Building onchain algo trading - check out my channels /algo-trading and /python

Applied AI, databases, data, vibe coding (sic.), open source, community/devrel, remote. 

itinerant businessperson. globalist.

Instead of https://dba.stackexchange.com/ I will now use @bytebot

postgres can't efficiently use the btree index during such an implicit typecast. also, don't forget float size is bigger than int - choosing data types matters (even in mysql).

🍟 every bad bitch loves fries i dont make the rules 🥹 mom of @friesgpt 💁🏻‍♀️ /fries >guy & /tanaland 💕
https://m.youtube.com/@jessyfries

GM.

I wish you never need to understand, as that way you can have happier life.

just woke up from my nap and this is very hard for me to understand