ODBC PSQL Options: Use Declare/Fetch, Cache Size

justindallasverizon — Thu, 13 Nov 2025 19:54:15 GMT

Hello Folks,

I have a QlikSense installation that connects to a Postgres db. Frequently, we get the following error:

Error: Connector reply error: SQL##f - SqlState: S1001, ErrorCode: 4, ErrorMsg: Out of memory while reading tuples.; memory allocation error???

This error seems to come from the ODBC running out of memory.

The solution from various forums seems to be to set Use Declare/Fetch => 1/Checked, and to set the Cache Size=100000

Does anyone know if setting such options on an ODBC will work with Qlik?

Any help is greatly appreciated.

Re: ODBC PSQL Options: Use Declare/Fetch, Cache Size

andy449holland — Wed, 19 Nov 2025 10:40:09 GMT

Hello,

The error you are encountering in Qlik Sense, “Out of memory while reading tuples,” typically occurs when the PostgreSQL ODBC driver attempts to fetch an entire large result set into memory at once. This can be mitigated by enabling the Use Declare/Fetch option in the ODBC settings, which allows the driver to use server-side cursors and fetch rows in smaller chunks instead of loading all rows at once. Alongside this, setting the Cache Size to a high value, such as 100,000, determines how many rows are fetched per round trip from the server, balancing memory usage and performance. Both settings are supported by Qlik Sense and can help prevent memory allocation errors while working with large datasets. E-ZPass New Hampshire

Best Regards

topic Re: ODBC PSQL Options: Use Declare/Fetch, Cache Size in Management & Governance

ODBC PSQL Options: Use Declare/Fetch, Cache Size

Re: ODBC PSQL Options: Use Declare/Fetch, Cache Size