AW: LIMIT in DECLARE CURSOR: request for comments - Mailing list pgsql-hackers

From Zeugswetter Andreas SB
Subject AW: LIMIT in DECLARE CURSOR: request for comments
Date
Msg-id 11C1E6749A55D411A9670001FA6879633680D9@sdexcsrv1.f000.d0188.sd.spardat.at
Whole thread Raw
List pgsql-hackers
> >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


pgsql-hackers by date:

Previous
From: Adriaan Joubert
Date:
Subject: Re: Re: BIT/BIT VARYING status
Next
From: Philip Warner
Date:
Subject: Re: AW: LIMIT in DECLARE CURSOR: request for comments