Re: [PERFORM] Dataset is fetched from cache but still takes sametime to fetch records as first run - Mailing list pgsql-performance

From Glyn Astill
Subject Re: [PERFORM] Dataset is fetched from cache but still takes sametime to fetch records as first run
Date
Msg-id 1114378459.249712.1498204379460@mail.yahoo.com
Whole thread Raw
List pgsql-performance
>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

pgsql-performance by date:

Previous
From: Tom Lane
Date:
Subject: Re: [PERFORM] Dataset is fetched from cache but still takes same time to fetch records as first run
Next
From: Akihiko Odaki
Date:
Subject: [PERFORM] Inappropriate inner table for nested loop join