Database Tool Window pagination behavior for large result sets

PhpStorm manages the retrieval of large datasets through the Database tool window by implementing a fetch limit, controlled by the Page Size setting. This mechanism prevents JVM memory exhaustion by bounding the initial query result set.

When working with datasets that exceed the global page size, the IDE allows for manual increases or the use of the 'Fetch All' command. However, the efficiency of this process depends on whether the underlying driver utilizes server-side cursors or relies on client-side buffering.

There is uncertainty regarding the memory impact when transitioning from paginated views to a full dataset fetch for extremely large tables.

• Does the IDE implement an internal threshold to warn users before a 'Fetch All' operation triggers a heap memory overflow?
• How does the pagination behavior differ between drivers that support server-side cursors versus those requiring client-side buffering?