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
Subject: Re: Dataset is fetched from cache but still takes same time to fetch
 records as first run
In-reply-to: 
 <CABUL136B8cKAxqaBh_2bHZXCOhRs8jOrAQP99DQ9RnE7xweucA@mail.gmail.com>
References: 
 <CABUL137pc8pfW+KLm=7ucXpSDi_eG2qWiFMdR-3-UMEkZ=QUqA@mail.gmail.com>
 <CAK17Jmm6WBXy-4-_H21PAopoU5o=FyoLwjBkPeJCNHCU59z-Qw@mail.gmail.com>
 <CABUL136B8cKAxqaBh_2bHZXCOhRs8jOrAQP99DQ9RnE7xweucA@mail.gmail.com>
Comments: In-reply-to Sumeet Shukla <sumeet.k.shukla@gmail.com>
	message dated "Thu, 22 Jun 2017 23:35:29 -0500"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <19640.1498193431.1@sss.pgh.pa.us>
Date: Fri, 23 Jun 2017 00:50:31 -0400
Message-ID: <19641.1498193431@sss.pgh.pa.us>
Precedence: bulk
Sender: pgsql-performance-owner@postgresql.org

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.

			regards, tom lane


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