> >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] Andreas
- AW: [HACKERS] LIMIT in DECLARE CURSOR: request for ... Zeugswetter Andreas SB
- Re: AW: [HACKERS] LIMIT in DECLARE CURSOR: req... Stephan Szabo
- Re: AW: [HACKERS] LIMIT in DECLARE CURSOR: req... Zeugswetter Andreas SB
- Re: AW: [HACKERS] LIMIT in DECLARE CURSOR:... Philip Warner
- AW: [HACKERS] LIMIT in DECLARE CURSOR: request... Zeugswetter Andreas SB