Re: Dataset is fetched from cache but still takes same time to fetch records as first run

From: Adam Brusselback <adambrusselback(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Sumeet Shukla <sumeet(dot)k(dot)shukla(at)gmail(dot)com>, Dave Stibrany <dstibrany(at)gmail(dot)com>, pgsql-performance(at)postgresql(dot)org
Subject: Re: Dataset is fetched from cache but still takes same time to fetch records as first run
Date: 2017-06-23 12:09:49
Message-ID: CAMjNa7dpP4Smz0KSGCWbxK_8_9WUETY5wuzmn=FRKaGZGTHtxA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

On Fri, Jun 23, 2017 at 12:50 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> It's possible that pgAdmin4 has improved matters in this area.
>

Sadly, not in my experience. It's actually considerably worse than
pgAdminIII in my experience when selecting a lot of rows, especially when
very wide (20+ columns).

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Albe Laurenz 2017-06-23 13:05:49 Re: Inappropriate inner table for nested loop join
Previous Message Akihiko Odaki 2017-06-23 11:54:39 Re: Inappropriate inner table for nested loop join