[
https://issues.apache.org/jira/browse/NIFI-1931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17812423#comment-17812423
]
Dmitry Dmitriev commented on NIFI-1931:
---------------------------------------
Hi!
We experience the same issue here.
Would it be possible to add either a property "AutoCommit" to the
QueryDatabaseTable processor, so that it can be switched off for Postgresql? Or
add custom code that will switch AutoCommit property off before starting the
processing?
There are some ideas here on how it can be done
[https://stackoverflow.com/questions/17475105/when-does-the-postgresql-jdbc-driver-fetch-rows-after-executing-a-query]
Any ideas appreciated! Thank you!
Dmitry
> QueryDatabaseTable processor; setFetchSize not working for postgres driver
> causing out of memory
> ------------------------------------------------------------------------------------------------
>
> Key: NIFI-1931
> URL: https://issues.apache.org/jira/browse/NIFI-1931
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Affects Versions: 0.6.1
> Reporter: Paul Bormans
> Priority: Major
>
> With NIFI-1691 the ability to specify the fetch size is added. However for
> postgres driver (or at least for postgresql-9.4.1208.jre6.jar) this seems not
> to be working since after some time out of memory is reported in the logs.
> See https://jdbc.postgresql.org/documentation/head/query.html also for some
> constraints; like auto commit needs to be set to False.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
