From: | David Fetter <david(at)fetter(dot)org> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Merlin Moncure <mmoncure(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Emanuel Calvo Franco <postgres(dot)arg(at)gmail(dot)com>, postgresql Forums <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: limit-offset different result sets with same query |
Date: | 2009-05-10 08:03:25 |
Message-ID: | 20090510080325.GB18067@fetter.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Sat, May 09, 2009 at 01:28:03PM -0400, Tom Lane wrote:
> Merlin Moncure <mmoncure(at)gmail(dot)com> writes:
> > On Fri, May 8, 2009 at 5:40 PM, Alvaro Herrera
> > <alvherre(at)commandprompt(dot)com> wrote:
> >> Yeah, we went over this on the spanish list, turned out that I
> >> couldn't remember about syncscan :-)
>
> > I like the new behavior. It really encourages proper use of order
> > by, because the natural ordering results are effectively
> > randomized. A class of subtle bugs has been made obvious. :)
>
> Not really, because the syncscan behavior only kicks in when your
> table gets large ... you'll never see it during devel testing on toy
> tables ...
Good point. It's important not to test only on toy-sized tables for
lots and lots of good reasons, scale-dependence of sync scans being a
small one.
Cheers,
David.
--
David Fetter <david(at)fetter(dot)org> http://fetter.org/
Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter
Skype: davidfetter XMPP: david(dot)fetter(at)gmail(dot)com
Remember to vote!
Consider donating to Postgres: http://www.postgresql.org/about/donate
From | Date | Subject | |
---|---|---|---|
Next Message | Alban Hertroys | 2009-05-10 10:38:55 | Re: A question about RAISE NOTICE |
Previous Message | Eric Smith | 2009-05-10 04:11:20 | Re: getting a list of users |