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

From ldh@laurent-hasson.com
Subject Re: [PERFORM] Dataset is fetched from cache but still takes same timeto fetch records as first run
Date
Msg-id BN4PR15MB0547CEA4CDCD3067EECD9A3285D80@BN4PR15MB0547.namprd15.prod.outlook.com
Whole thread Raw
In response to Re: [PERFORM] Dataset is fetched from cache but still takes same timeto fetch records as first run  (Adam Brusselback <adambrusselback@gmail.com>)
List pgsql-performance
ditto here... much slower, and crashes too often. We run an evergreen shop where I work, but everyone has moved back to III.

Sent from my BlackBerry KEYone - the most secure mobile device
From: adambrusselback@gmail.com
Sent: June 23, 2017 8:11 AM
To: tgl@sss.pgh.pa.us
Cc: sumeet.k.shukla@gmail.com; dstibrany@gmail.com; pgsql-performance@postgresql.org
Subject: Re: [PERFORM] Dataset is fetched from cache but still takes same time to fetch records as first run

On Fri, Jun 23, 2017 at 12:50 AM, Tom Lane <tgl@sss.pgh.pa.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).

pgsql-performance by date:

Previous
From: Albe Laurenz
Date:
Subject: Re: [PERFORM] Inappropriate inner table for nested loop join
Next
From: Chris Wilson
Date:
Subject: [PERFORM] Fwd: Slow query from ~7M rows, joined to two tables of ~100 rows each