RE: [HACKERS] Solution for LIMIT cost estimation

> -----Original Message-----
> From: owner-pgsql-hackers@postgresql.org
> [mailto:owner-pgsql-hackers@postgresql.org]On Behalf Of Tom Lane
> 
> Philip Warner <pjw@rhyme.com.au> writes:
> > Just my 0.02c, but I don't like putting limits on an optimizer. 
> 
> That's my feeling too.  I'm leaning towards letting the optimizer do the
> best it can with the given query (which means using OFFSET+LIMIT as the
> estimated number of tuples to be fetched), 

What about cursors ?
I heard from Jan that we could specify 'LIMIT ALL'  to tell optimizer that
the response to get first rows is needed.

Regards.

Hiroshi Inoue
Inoue@tpf.co.jp