IN is not recommended. Use = ANY instead.

codesnik · 2025-05-04T04:04:21 1746331461

aren't they the same in Postgres?

frollogaston · 2025-05-04T05:13:49 1746335629

Yes, according to the manual, IN is equivalent to = ANY() https://www.postgresql.org/docs/current/functions-subquery.h...

I had to check because for some reason, I always thought =ANY was somehow better than IN.

Sesse__ · 2025-05-04T09:39:05 1746351545

IN is fine. The biggest problem comes with NOT IN, which has NULL semantics that makes life difficult for the planner. It is consistent but rarely what the user wants. NOT EXISTS is typically better there.

tczMUFlmoNk · 2025-05-04T06:28:04 1746340084

ANY can be used with arrays, particularly query parameters: `id = ANY($1::int[])`, but not `id IN $1::int[]`.

frollogaston · 2025-05-04T22:08:10 1746396490

Oh that must be why I got into this habit.

masklinn · 2025-05-04T05:47:18 1746337638

It is, but in a pretty minor way: any can be used with no items, IN can not and will error.