| From: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com> |
|---|---|
| To: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
| Cc: | PostgreSQL mailing lists <pgsql-odbc(at)postgresql(dot)org> |
| Subject: | Re: About FetchBufferSize and row caching for postgres odbc |
| Date: | 2013-08-15 17:11:25 |
| Message-ID: | 520D0BBD.7060700@vmware.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-odbc |
On 14.08.2013 08:26, Michael Paquier wrote:
> I got a couple of questions about the use of FetchBufferSize (one of
> the settings of odbc.ini) and row caching in pgodbc.
>
> Depending on the driver used with ODBC, sometimes FetchBufferSize
> means the maximum number of rows, or a maximum size of data that can
> be kept on cache on client side. Which definition of FetchBufferSize
> does pgodbc use? I assume the max number of rows... But I couldn't
> figure out which one it is even by looking at the pgodbc documentation
> like the one on pgfoundry
psqlodbc doesn't have a parameter called "FetchBufferSize". Setting that
in odbc.ini will therefore have no effect. There is a parameter called
"Fetch", which sets the number of rows to fetch.
- Heikki
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2013-08-15 23:57:46 | Re: About FetchBufferSize and row caching for postgres odbc |
| Previous Message | Heikki Linnakangas | 2013-08-15 17:08:55 | Re: Calling a stored procedure with an array parameter |