From: | Emanuel Calvo Franco <postgres(dot)arg(at)gmail(dot)com> |
---|---|
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>, David Fetter <david(at)fetter(dot)org>, postgresql Forums <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: limit-offset different result sets with same query |
Date: | 2009-05-11 12:19:37 |
Message-ID: | f205bb120905110519n6b2d7b4brc2ce3c7aa4ca2fcc@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
2009/5/9 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>:
> 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 ...
>
> regards, tom lane
>
Yeap. If you see one of the test i made, you'll see this switch over the
~100 regs.
--
Emanuel Calvo Franco
Sumate al ARPUG !
( www.arpug.com.ar)
ArPUG / AOSUG Member
From | Date | Subject | |
---|---|---|---|
Next Message | Jasen Betts | 2009-05-11 13:00:23 | Re: Remote access |
Previous Message | Jasen Betts | 2009-05-11 09:02:30 | Re: Controlling psql output |