From: | Peter Geoghegan <peter(at)2ndquadrant(dot)com> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: effective_io_concurrency |
Date: | 2012-08-30 20:25:44 |
Message-ID: | CAEYLb_UQddZKh+x3d=ugCCHBykGndfjQaOhx2ox21hsvB3HBmQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 30 August 2012 20:28, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> On Sat, Jul 28, 2012 at 4:09 PM, Jeff Janes <jeff(dot)janes(at)gmail(dot)com> wrote:
>> But it might be better yet to make ordinary index scans benefit from
>> effective_io_concurrency, but even if/when that gets done it would
>> probably still be worthwhile to make the planner understand the
>> benefit.
>
> That sounds good too, but separate.
Indeed. The original effective_io_concurrency commit message said:
"""
***SNIP***
(The best way to handle this for plain index scans is still under debate,
so that part is not applied yet --- tgl)
"""
...seems like a pity that this debate never reached a useful conclusion.
Just how helpful is effective_io_concurrency? Did someone produce a
benchmark at some point?
--
Peter Geoghegan http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training and Services
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2012-08-30 20:27:17 | Re: --disable-shared is entirely broken these days |
Previous Message | Robert Haas | 2012-08-30 20:21:57 | Re: Fix for gistchoose |