Date: Fri, 23 Jun 2017 07:52:59 +0000 (UTC)
From: Glyn Astill <glynastill@yahoo.co.uk>
Reply-To: Glyn Astill <glynastill@yahoo.co.uk>
To: Tom Lane <tgl@sss.pgh.pa.us>, Sumeet Shukla <sumeet.k.shukla@gmail.com>
Cc: Dave Stibrany <dstibrany@gmail.com>,
	"pgsql-performance@postgresql.org" <pgsql-performance@postgresql.org>
Message-ID: <1114378459.249712.1498204379460@mail.yahoo.com>
Subject: Re: Dataset is fetched from cache but still takes same
 time to fetch records as first run
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
References: <1114378459.249712.1498204379460.ref@mail.yahoo.com>
Content-Length: 897
Precedence: bulk
Sender: pgsql-performance-owner@postgresql.org

>From: Tom Lane <tgl@sss.pgh.pa.us>
>To: Sumeet Shukla <sumeet.k.shukla@gmail.com>
>Cc: Dave Stibrany <dstibrany@gmail.com>; pgsql-performance@postgresql.org
>Sent: Friday, 23 June 2017, 5:50
>Subject: Re: [PERFORM] Dataset is fetched from cache but still takes same time to fetch records as first run
> Sumeet Shukla <sumeet.k.shukla@gmail.com> writes:>
>> Yes, but when I actually execute the query in pgAdmin3, it takes exactly
>> the same time of 19.5 secs.
>
>pgAdmin is well known to be horribly inefficient at displaying large
>query results (and 121788 rows qualifies as "large" for this purpose,
>I believe).  The circa-tenth-of-a-second savings on the server side
>is getting swamped by client-side processing.
>
>It's possible that pgAdmin4 has improved matters in this area.

>

It's also possibly time taken for the results to be tranferred over a network if the data is large.

Glyn


-- 
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance