From: | Markus Angst <mangst(at)inventec(dot)ch> |
---|---|
To: | pgsql-odbc(at)lists(dot)postgresql(dot)org |
Subject: | Re: Out of memory while reading tuples |
Date: | 2018-11-06 16:10:27 |
Message-ID: | e100eabc-2688-a9e6-9380-c144e92ebb31@inventec.ch |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-odbc |
Hi Hiroshi,
>>> Postgres 10.4 64bit on Windows
>>> psqlODBC 10.03.0000
>>> - Use Declare/Fetch is off
>>> - Cache size is 10'000'000
>>>
>>> Issuing a simple select statement with Microsoft Access gives me the
>>> following ODBC error:
>>>
>>> "Out of memory while reading tuples.; memory allocation error??? (#4)"
>>>
>>> The statement returns 822701 rows (via JDBC), average row size is 100
>>> bytes.
>>>
>>> On https://odbc.postgresql.org/docs/config.html it says:
>>> "Cache Size: When using cursors, this is the row size of the tuple
>>> cache. If not using cursors, this is how many tuples to allocate
>>> memory for at any given time. The default is 100 rows for either case."
>>
>> Hmm, it seems a documentation bug to me.
>>
>> "If not using cursors, this is how many tuples to allocate memory at
>> first."
>>
>> seems correct.
>
> Oops, I was wrong.
>
> "If not using cursors, this has no meaning."
>
> seems right.
Thanks for your reply. What is the exact memory limit (and, out of curiosity:
why does it exist)?
Regards
Markus Angst
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2018-11-06 16:29:25 | Re: SQLExecDirectW returns SQL_SUCCESS even if sql finishes with error |
Previous Message | Juan Tiritas | 2018-11-06 13:49:33 | Does the psqlodbc driver support asynchronous queries? |