[Feature Request]: Introduce Configurable Row Limit and Pagination for Query Results
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- postgresql
- Domain
- databases
Research direction
The issue names no files, tests, or entry points. Start by locating the PostgreSQL extension's query execution and result-display paths, then determine where a global row-limit setting and pagination would belong; done means large query results honor the configured default and can be paged without manual LIMIT clauses.
Written by the indexing model from the issue text.
Description
Feature Description:
I would like the PostgreSQL extension to provide an option to set a global default row limit for query results and support pagination when displaying large datasets. Please add an optional global setting to specify a default row limit for all queries (e.g., 1000 rows), similar to DBeaver’s behavior.
This would help me because it would prevent accidental full-table scans, improve performance, and make working with large tables more efficient without manually adding LIMIT clauses every time.
Problem and Motivation:
Currently, I'm unable to enforce a default row limit across all queries in the PostgreSQL extension.
This causes me to risk performance issues and long-running queries when fetching large datasets.
With this feature, I could safely explore data without worrying about overwhelming the client or database, and I could navigate large result sets easily using pagination.
- Dominant language
- No language data
- Stars
- 395
- Forks
- 33
- Avg merge
- 1h 46m
- Merged PRs (30d)
- 3
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from microsoft/vscode-pgsql
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
microsoft/vscode-pgsql#190 · 3 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
microsoft/vscode-pgsql#307 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 55/100
microsoft/vscode-pgsql#306 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 68/100
microsoft/vscode-pgsql#305 · 2 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
microsoft/vscode-pgsql#302 ·
All issues in microsoft/vscode-pgsql
Similar issues
-
documentation help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
OpenLiberty/open-liberty#35839 ·
-
affects-9.0 found-by-ai may-affects-25.10 may-affects-26.3 may-affects-26.9 may-affects-7.5 may-affects-8.1 may-affects-8.5 severity/major sig/execution type/bug
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
antlr/grammars-v4#5014 · 1 comment ·