In the edit grid, pgAdmin should check the estimated number of rows of the table. If it's more than a specific limit, it should ask if the user still wants to load that number of rows. The user should be able to cancel the query or to force the retrieving of the rows (for example if the estimated number of rows is wrong).
We can probably do the same thing in the query tool by checking the number of rows that will be returned before loading them in the grid
Issue migrated from Redmine: https://redmine.postgresql.org/issues/517 Originally created by Anonymous at 2010-10-31 06:21:50 UTC.
In the edit grid, pgAdmin should check the estimated number of rows of the table. If it's more than a specific limit, it should ask if the user still wants to load that number of rows. The user should be able to cancel the query or to force the retrieving of the rows (for example if the estimated number of rows is wrong).
We can probably do the same thing in the query tool by checking the number of rows that will be returned before loading them in the grid