Re: pgsql/src/backend/nodes (copyfuncs.c outfuncs.c print.c)
От | Hiroshi Inoue |
---|---|
Тема | Re: pgsql/src/backend/nodes (copyfuncs.c outfuncs.c print.c) |
Дата | |
Msg-id | 39F8D0A4.A9A22EE1@tpf.co.jp обсуждение исходный текст |
Ответ на | pgsql/src/backend/nodes (copyfuncs.c outfuncs.c print.c) (Tom Lane <tgl@postgresql.org>) |
Ответы |
Re: pgsql/src/backend/nodes (copyfuncs.c outfuncs.c print.c)
Re: pgsql/src/backend/nodes (copyfuncs.c outfuncs.c print.c) |
Список | pgsql-committers |
Tom Lane wrote: > Hiroshi Inoue <Inoue@tpf.co.jp> writes: > > It seems to me that LIMIT in declare cursor statement is only > > for optimizer's hint. > > I think that would just confuse people. It could be. However what does LIMIT mean ? Rows per FETCH ? Probably no. FETCH forward,backward,forward,backward,.... and suddenly EOF ? > If we want to have a hint > that says "optimize for fast start", it ought to be done in another > way than saying that SELECT ... LIMIT means different things in > different contexts. > Yes I want to give optimizer a hint "return first rows fast". When Jan implemented LIMIT first,there was an option "LIMIT ALL" and it was exactly designed for the purpose. Regards. Hiroshi Inoue
В списке pgsql-committers по дате отправления: