Response time issues while exporting data

[LaxManan1]

Dear all, I was trying to export the data returned by a sub optimal query in dbeaver. The query ran for 24m+. Then while exporting, the task took equally same time (in fact it is still running at 29minutes+, after I clicked "Proceed" in the Export Data window.

As you can see from screenshot, I have the buffer (?) set at 30,000 rows. The result set was 424 rows. My recommendation would be to have a buffer (memory) in dbeaver, and hold it for say, x minutes. Users need to know that the underlying data may have changed, but the memory may be just pushed to csv quickly, who acknowledges that they may be looking at data which is stale. It is a zero risk item for me/users who perform similar tasks. I dont know, at this stage if the connections is alive. But the green bar has been moving for minutes now.

Please let me know if there is already a setting which let dbeaver do exactly what I described.

[davestokes]

@LaxManan1 Thank you for your idea. You might want to set the heap size to something larger than the default 1024m, maybe 4096m.

We wonder how many users seek this feature.
So, for someone who is interested, please vote for the issue with 👍🏻under the issue description to promote it to a higher priority.

[E1izabeth]

Hi, @LaxManan1!
Please try checking Use fetched rows setting. It looks like what you need. Let me know if it satisfies your request.

[LaxManan1]

Hi E1izabeth, Yes that solved the issue. Thanks.

…

On Thu, Aug 6, 2026 at 6:19 PM Elizabeth ***@***.***> wrote: *E1izabeth* left a comment (dbeaver/dbeaver#41677) <#41677 (comment)> Hi, @LaxManan1 <https://github.com/LaxManan1>! Please try checking Use fetched rows setting. It looks like what you need. Let me know if it satisfies your request. Image: Image (view on web) <https://github.com/user-attachments/assets/ed05e5fe-946d-4d69-9e48-e1c01c50d186> — Reply to this email directly, view it on GitHub <#41677?email_source=notifications&email_token=AHMEJFJGGG6P6NI5NFAEHQD5ISHXHA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKMRQGU4TCMRYGI2KM4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJLDGN5XXIZLSL5RWY2LDNM#issuecomment-5205912824>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AHMEJFJQUVRVU2QCUXTSKNL5ISHXHAVCNFSNUABEKJSXA33TNF2G64TZHM2DINRWGI3DMOJ3JFZXG5LFHM2TANJYGQ4TQNZUGOQXMAQ> . Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS <https://github.com/notifications/mobile/ios/AHMEJFLIYAOETEHSFTJHHDL5ISHXHA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKMRQGU4TCMRYGI2KM4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJKTGN5XXIZLSL5UW64Y> and Android <https://github.com/notifications/mobile/android/AHMEJFOYTGABIQKDJLT376T5ISHXHA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKMRQGU4TCMRYGI2KM4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJLTGN5XXIZLSL5QW4ZDSN5UWI>. Download it today! You are receiving this because you were mentioned.Message ID: ***@***.***>