Re: Data grid: fetching/scrolling data on user demand

From: Dave Page <dpage(at)pgadmin(dot)org>
To: legrand legrand <legrand_legrand(at)hotmail(dot)com>
Cc: pgAdmin Support <pgadmin-support(at)postgresql(dot)org>
Subject: Re: Data grid: fetching/scrolling data on user demand
Date: 2017-10-17 09:00:46
Message-ID: CA+OCxox5jSeAg2mXnbuFfsybv6bJKFoiga-DX3Dx-o1y---OeQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgadmin-support

On Tue, Oct 17, 2017 at 9:51 AM, legrand legrand <
legrand_legrand(at)hotmail(dot)com> wrote:

> 1000 first rows are available in less than zone second.
> See query with limit 1000.
>

We cannot add arbitrary limit/offsets to users queries. They will affect
timing for those who are trying to tune queries, and may well affect other
behaviours. Not to mention the fact that the user might be running a
complex script that we would have to parse client-side to try to figure out
where to add the limit/offset (and likely get it wrong).

> Monitoring memory usage or PG_stat_activity shows that all the data is
> fetched.

Sure - pg_stat_activity (it's all lower case) will show the connection
state as idle. But the point is - until it does, the query is still being
processed and we don't get the data.

--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake

EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Browse pgadmin-support by date

  From Date Subject
Next Message Murtuza Zabuawala 2017-10-17 09:05:08 Re: Data grid: fetching/scrolling data on user demand
Previous Message legrand legrand 2017-10-17 08:51:43 Re: Data grid: fetching/scrolling data on user demand