Re: FETCH FIRST clause PERCENT option
От | Tomas Vondra |
---|---|
Тема | Re: FETCH FIRST clause PERCENT option |
Дата | |
Msg-id | 4a1f303c-26ba-2de9-b6ed-d16ef1c21b36@2ndquadrant.com обсуждение исходный текст |
Ответ на | Re: FETCH FIRST clause PERCENT option (Surafel Temesgen <surafel3000@gmail.com>) |
Ответы |
Re: FETCH FIRST clause PERCENT option
|
Список | pgsql-hackers |
On 1/30/19 7:07 AM, Surafel Temesgen wrote: > > > On Mon, Jan 28, 2019 at 1:28 AM Tomas Vondra > <tomas.vondra@2ndquadrant.com <mailto:tomas.vondra@2ndquadrant.com>> wrote: > > > > OK. Does that mean you agree the incremental approach is reasonable? > > > there are no noticeable performance difference but i love previous > approach more regarding cursor operation it fetch tuple forward and > backward from tuplestore only but in incremental approach we have to > re execute outer node in every forward and backward fetching operation > I'm not sure I understand - are you saying every time the user does a FETCH, we have to run the outer plan from scratch? I don't see why would that be necessary? And if it is, how come there's no noticeable performance difference? Can you share a patch implementing the incremental approach, and a query demonstrating the issue? regards -- Tomas Vondra http://www.2ndQuadrant.com PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
В списке pgsql-hackers по дате отправления: