| From: | Michael Meskes <meskes(at)postgresql(dot)org> |
|---|---|
| To: | Boszormenyi Zoltan <zb(at)cybertec(dot)at> |
| Cc: | Noah Misch <noah(at)leadboat(dot)com>, Michael Meskes <meskes(at)postgresql(dot)org>, Robert Haas <robertmhaas(at)gmail(dot)com>, PG Hackers <pgsql-hackers(at)postgresql(dot)org>, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us> |
| Subject: | Re: ECPG FETCH readahead |
| Date: | 2012-04-17 04:48:19 |
| Message-ID: | 20120417044819.GA9043@feivel.credativ.lan |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Apr 17, 2012 at 06:02:34AM +0200, Boszormenyi Zoltan wrote:
> I listed two scenarios.
> 1. occasional bump of the readahead window for large requests,
> for smaller requests it uses the originally set size
> 2. permanent bump of the readahead window for large requests
> (larger than previously seen), all subsequent requests use
> the new size
>
> Both can be implemented easily, which one do you prefer?
> If you always use very large requests, 1) behaves like 2)
I'd say let's go for #2. #1 is probably more efficient but not what the
programmer asked us to do. After all it's easy to increase the window size
accordingly if you want so as a programmer.
Michael
--
Michael Meskes
Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
Michael at BorussiaFan dot De, Meskes at (Debian|Postgresql) dot Org
Jabber: michael.meskes at googlemail dot com
VfL Borussia! Força Barça! Go SF 49ers! Use Debian GNU/Linux, PostgreSQL
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2012-04-17 04:56:13 | Re: Why can't I use pgxs to build a plpgsql plugin? |
| Previous Message | Boszormenyi Zoltan | 2012-04-17 04:02:34 | Re: ECPG FETCH readahead |