> >So I think if you want to make optimization decisions based on cursors
> >being used versus a "normal" select, then the only thing you can safely
> >take into account is the network roundtrip and client processing per
> >fetch, but that might be as random as anything.
> Which is why I like the client being able to ask the
> optimizer for certain kinds of solutions *explicitly*.
Yes, something like:
set optimization to [first_rows|all_rows]
pgsql-hackers by date
|Next:||From: Philip Warner||Date: 2000-10-31 13:23:53|
|Subject: Re: AW: LIMIT in DECLARE CURSOR: request for comments|
|Previous:||From: Adriaan Joubert||Date: 2000-10-31 11:51:34|
|Subject: Re: Re: BIT/BIT VARYING status|