Re: How bad is using queries with thousands of values for operators IN or ANY?

On Mon, 2020-08-31 at 10:04 +0200, Thorsten Schöning wrote:
> I have lots of queries in which I need to restrict access to rows
> using some decimal row-ID and am mostly doing so with using the
> operator IN in WHERE-clauses. Additionally I'm mostly embedding the
> IDs as ","-seperated list into the query directly, e.g. because I
> already hit a limitation of ~32k parameters of the JDBC-driver[1] for
> Postgres.

Is it an option to change that usage pattern?

Very often this is some kind of "poor man's join": first select all
rows from table A that match a certain condition, then select all
rows from B where the foreign key matches any IDs from the first query.

Yours,
Laurenz Albe
--
Cybertec | https://www.cybertec-postgresql.com