RE: [HACKERS] Solution for LIMIT cost estimation

From: "Hiroshi Inoue" <Inoue(at)tpf(dot)co(dot)jp>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: <pgsql-hackers(at)postgresql(dot)org>, "Philip Warner" <pjw(at)rhyme(dot)com(dot)au>
Subject: RE: [HACKERS] Solution for LIMIT cost estimation
Date: 2000-02-15 01:00:04
Message-ID: 000301bf774f$feb8aa20$2801007e@tpf.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> -----Original Message-----
> From: owner-pgsql-hackers(at)postgresql(dot)org
> [mailto:owner-pgsql-hackers(at)postgresql(dot)org]On Behalf Of Tom Lane
>
> Philip Warner <pjw(at)rhyme(dot)com(dot)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(at)tpf(dot)co(dot)jp

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Don Baccus 2000-02-15 01:00:12 Re: [HACKERS] Solution for LIMIT cost estimation
Previous Message Don Baccus 2000-02-15 00:54:48 Re: [HACKERS] Solution for LIMIT cost estimation