From: | Dave Cramer <pg(at)fastcrypt(dot)com> |
---|---|
To: | John Kew <jkew(at)tableau(dot)com> |
Cc: | "pgsql-odbc(at)postgresql(dot)org" <pgsql-odbc(at)postgresql(dot)org> |
Subject: | Re: Anecdotal JDBC vs ODBC bulk export performance |
Date: | 2016-01-05 11:36:37 |
Message-ID: | CADK3HHJMDM9kjtiEUZzPwc2zDk6kGqsh5TFuL2hgjg9bPzFhDg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-odbc |
Hi John,
If you just want speed you could try the copy option.
It would appear that the copy documentation seems to have disappeared, but
the API docs are here
https://jdbc.postgresql.org/documentation/publicapi/index.html
Dave Cramer
davec(at)postgresintl(dot)com
www.postgresintl.com
On 4 January 2016 at 15:37, John Kew <jkew(at)tableau(dot)com> wrote:
> The open source JDBC driver appears to outperform the ODBC driver when
> executing bulk extract queries of the form: "SELECT * from [Blah] Limit
> [n]" - We are just measuring the raw rows per second from this query for
> pulling all the rows out. After playing with the FetchSize in the ODBC
> driver we have improved performance significantly but are there any other
> techniques; tools or tips which you would suggest for further improving
> performance?
>
>
> ReadOnly does not appear to have a significant effect. The JDBC connection
> string is using the default settings and setFetchSize is not called on the
> JDBC driver. We have not yet started profiling the ODBC driver. For this
> quick test we are also not using column binding on the ODBC side; but we
> are calling SQLFetch to count the total # of rows returned. Essentially the
> same thing occurs on the JDBC side.
>
>
> -John
>
From | Date | Subject | |
---|---|---|---|
Next Message | Hiroshi Saito | 2016-01-10 15:23:09 | psqlODBC 09.05.0100 Released |
Previous Message | John Kew | 2016-01-04 20:37:37 | Anecdotal JDBC vs ODBC bulk export performance |