| From: | "ldh(at)laurent-hasson(dot)com" <ldh(at)laurent-hasson(dot)com> |
|---|---|
| To: | Adam Brusselback <adambrusselback(at)gmail(dot)com>, 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-performa(dot) <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 16:55:03 |
| Message-ID: | BN4PR15MB0547CEA4CDCD3067EECD9A3285D80@BN4PR15MB0547.namprd15.prod.outlook.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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(at)gmail(dot)com
Sent: June 23, 2017 8:11 AM
To: tgl(at)sss(dot)pgh(dot)pa(dot)us
Cc: sumeet(dot)k(dot)shukla(at)gmail(dot)com; dstibrany(at)gmail(dot)com; pgsql-performance(at)postgresql(dot)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(at)sss(dot)pgh(dot)pa(dot)us<mailto: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).
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Chris Wilson | 2017-06-23 20:09:57 | Fwd: Slow query from ~7M rows, joined to two tables of ~100 rows each |
| Previous Message | Albe Laurenz | 2017-06-23 13:05:49 | Re: Inappropriate inner table for nested loop join |