Hi,

We are using PostGres and hibernate Search. Doing some load testing, I do a full text search on the data, and I expect about 60 000 results from the Lucene search. When Hibernate passes these results from the search query to the Jpa query as an "in('1', '2', '3', ...)" sql query, PostGres doesn't like the fact that there are 60 000 parameters in the list. Which is quite normal of course.

My question is, how can I limit the list of ids in the list passed to the Jpa query?

Thanks in advance,
Michael

Hi,
right the default loading strategy is not appropriate for large result sets.

We expect most use cases to use pagination, as with



often used in combination with

which provides an estimate of the full match size without actually loading them.

If you're sure you need to process all results, did you consider using instead the scrollable API ? because if you're not adding any boundary to the query you might get in out of memory too.

Also have a look into

Hi Sanne,

Thanks, I will give that a shot!

Kind regards,
Michael