Limit Page Size Handling Shifts Between GoLand 2023.3 and 2024.2 for MySQL and PostgreSQL Drivers

Goal

Determine whether GoLand’s ‘Limit page size’ setting reliably bounds result sets when using different JDBC drivers in recent versions.

Context

GoLand 2023.3 and 2024.2 expose a ‘Limit page size’ option under Settings > Database > Data Editor and Viewer. The IDE uses this value to request a limited block of rows from the server and then paginates client‑side as the user scrolls. Documentation states that the setting acts as a safety layer, but notes that some JDBC drivers may ignore the limit and return the full result set.

Uncertainty

It is unclear whether the observed driver‑specific behavior is consistent across GoLand 2023.3 and 2024.2, or whether a version‑specific change in the IDE’s database console alters how the limit is communicated to the driver. Additionally, there is no clear guidance on which driver versions respect the setting and which require an explicit SQL LIMIT clause.

Specific questions:

• Does GoLand 2024.2 enforce the ‘Limit page size’ value when the PostgreSQL JDBC driver 42.7.3 is used?
• Does the MySQL Connector/J 8.0.33 honor the setting, or does it fetch the entire result set regardless?
• Is there a reliable way to force client‑side pagination in GoLand without relying on the driver’s handling of the limit?