If I may add, please have pgAdmin display the total number of rows in the result set regardless of pagination page size.
On Mon, Jul 1, 2024 at 4:35 AM Usman Khan <umk...@gmail.com> wrote: > Hi Aditya > I vote for pagination, it would really be helpful for end users. > In addition to giving the user the ability to set page size, if he can > also select or enter what page he can jump to say 501, 990 etc it would be > helpful. > > On Fri, Jun 28, 2024 at 3:44 PM Aditya Toshniwal < > aditya.toshni...@enterprisedb.com> wrote: > >> Hi, >> >> Unfortunately, there were only 3 responses to this. >> In that case, we will discuss internally and decide what to do. >> >> On Thu, Jun 20, 2024 at 2:46 PM Aditya Toshniwal < >> aditya.toshni...@enterprisedb.com> wrote: >> >>> Hi Everyone, >>> >>> Request you to share your opinion on this and respond on: >>> >>> https://docs.google.com/forms/d/e/1FAIpQLSdfJhNK8qXSe9mKcubZa8jjjYl0hiZVxhv6GGJo8WJcYc27ug/viewform?usp=sharing >>> >>> On Thu, Jun 20, 2024 at 1:36 PM Dave Page <dp...@pgadmin.org> wrote: >>> >>>> Hi >>>> >>>> On Wed, 19 Jun 2024 at 13:42, Aditya Toshniwal < >>>> aditya.toshni...@enterprisedb.com> wrote: >>>> >>>>> Hi Hackers, >>>>> >>>>> Query tool data grid currently pulls the data on load basis in >>>>> batches. For example, it will initially load only 1000 rows and once a >>>>> user >>>>> scrolls to the 1000th row, it will fetch the next batch of 1000. >>>>> Many users who want access in between rows or last row struggle to do >>>>> it as the user has to scroll and scroll. If someone grabs the scroller and >>>>> pulls it down still it will be a good UX and the scrollbar may jump. One >>>>> reported here - https://github.com/pgadmin-org/pgadmin4/issues/1780 >>>>> One more aspect to this is the in memory data of the query tool which >>>>> keep on increasing on each scroll, it affects the performance. >>>>> >>>>> I propose we should use pagination instead of infinite scroll with the >>>>> following advantages: >>>>> 1. Users can jump to any page they want. >>>>> 2. Users can change the page size on the grid directly. >>>>> 3. Memory will be used only for visible rows so performance >>>>> improvement. >>>>> 4. Predictable UI, no jumping scrollbars. >>>>> >>>>> Let me know what you think. >>>>> >>>> >>>> >>>> I think there are definite benefits, but there is the downside of >>>> having to scroll and click to browse results. Personally I'm fine with >>>> that, but I think you should probably poll pgadmin-support for opinions >>>> from more users. >>>> >>>> -- >>>> Dave Page >>>> pgAdmin: https://www.pgadmin.org >>>> PostgreSQL: https://www.postgresql.org >>>> EDB: https://www.enterprisedb.com >>>> >>>> >>> >>> -- >>> Thanks, >>> Aditya Toshniwal >>> pgAdmin Hacker | Sr. Software Architect | *enterprisedb.com* >>> <https://www.enterprisedb.com/> >>> "Don't Complain about Heat, Plant a TREE" >>> >> >> >> -- >> Thanks, >> Aditya Toshniwal >> pgAdmin Hacker | Sr. Software Architect | *enterprisedb.com* >> <https://www.enterprisedb.com/> >> "Don't Complain about Heat, Plant a TREE" >> >
