Re: Sequential Scans

From: Ericson Smith <eric(at)did-it(dot)com>
To: Mark Kirkwood <markir(at)paradise(dot)net(dot)nz>
Cc: Richard Huxton <dev(at)archonet(dot)com>, Postgresql General <pgsql-general(at)postgresql(dot)org>
Subject: Re: Sequential Scans
Date: 2003-03-10 14:39:27
Message-ID: 1047307166.22672.27.camel@localhost.localdomain
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Well, actually... I shifted to using cursors instead of those LIMIT,
OFFSETS. Things are lightning fast now. In fact in many batch processing
operations, we are going to be using those cursors in the future.

- Ericson Smith
eric(at)did-it(dot)com

On Mon, 2003-03-10 at 05:45, Mark Kirkwood wrote:
> Richard Huxton wrote:
>
> >
> >
> > I think CPU_INDEX_TUPLE_COST may be your
> >friend (see archives for discussion).
> >
> >
> >
>
> Might be worth looking at RANDOM_PAGE_COST as well ( going down to 1 or
> even fractional values)
>
> best wishes
>
> Mark
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 5: Have you checked our extensive FAQ?
>
> http://www.postgresql.org/docs/faqs/FAQ.html
--
Ericson Smith <eric(at)did-it(dot)com>

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Robert Treat 2003-03-10 14:56:18 Re: Website main page empty
Previous Message greg 2003-03-10 14:34:56 Re: Export table/view in xml-format