Skip site navigation (1) Skip section navigation (2)

Re: ECPG FETCH readahead

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, Böszörményi Zoltán <zb(at)cybertec(dot)at>, Bruce Momjian <bruce(at)momjian(dot)us>, Michael Meskes <meskes(at)postgresql(dot)org>, PG Hackers <pgsql-hackers(at)postgresql(dot)org>, Hans-Juergen Schoenig <hs(at)cybertec(dot)at>
Subject: Re: ECPG FETCH readahead
Date: 2010-10-13 23:47:14
Message-ID: (view raw or whole thread)
Lists: pgsql-hackers
On Thu, Jun 24, 2010 at 8:19 AM, Michael Meskes <meskes(at)postgresql(dot)org> wrote:
> On Thu, Jun 24, 2010 at 12:04:30PM +0300, Heikki Linnakangas wrote:
>> Is there a reason not to enable it by default? I'm a bit worried
>> that it will receive no testing if it's not always on.
> Yes, there is a reason, namely that you don't need it in native mode at all.
> ECPG can read as many records as you want in one go, something ESQL/C
> apparently cannot do. This patch is a workaround for that restriction. I still
> do not really see that this feature gives us an advantage in native mode
> though.

So, who has the next action on this patch?  Does Zoltan need to revise
it, or does Michael need to review it, or where are we?


Robert Haas
The Enterprise PostgreSQL Company

In response to


pgsql-hackers by date

Next:From: Christian UllrichDate: 2010-10-14 00:30:43
Subject: Re: [GENERAL] Text search parser's treatment of URLs and emails
Previous:From: fazool meinDate: 2010-10-13 23:23:57
Subject: Timeline in the light of Synchronous replication

Privacy Policy | About PostgreSQL
Copyright © 1996-2015 The PostgreSQL Global Development Group