# JDBC Fetch size VS JDBC Page Size

**URL:** <https://discuss.elastic.co/t/jdbc-fetch-size-vs-jdbc-page-size/168530>\
**Category:** Logstash\
**Created:** [February 15, 2019, 6:40am UTC](https://discuss.elastic.co/t/jdbc-fetch-size-vs-jdbc-page-size/168530 "2019-02-15T06:40:26Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![kelvink](https://avatars.discourse-cdn.com/v4/letter/k/c68b51/32.png) [@kelvink](https://discuss.elastic.co/u/kelvink)\
**Post date:** [February 15, 2019, 6:40am UTC](https://discuss.elastic.co/t/jdbc-fetch-size-vs-jdbc-page-size/168530/1 "2019-02-15T06:40:26Z")

</div>

Hi there,

We're trying to understand what is the difference between the jdbc\_page\_size parameter and jdbc\_fetch\_size, for logstash input jdbc plugin . What I understood from testing is that jdbc\_page\_size determines the number of rows that are fetched from database per trip. I've tried changing jdbc\_fetch\_size parameter but nothing changes.  
Reason is that we faced JVM memory issues before when we were tweaking these parameters and would like a better understanding of what it does.

Thanks

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [March 15, 2019, 6:40am UTC](https://discuss.elastic.co/t/jdbc-fetch-size-vs-jdbc-page-size/168530/2 "2019-03-15T06:40:27Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.