| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
| Cc: | Alvaro Herrera <alvherre(at)commandprompt(dot)com>, David Fetter <david(at)fetter(dot)org>, 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-09 17:28:03 |
| Message-ID: | 9654.1241890083@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Eric Smith | 2009-05-10 00:00:18 | Re: getting a list of users |
| Previous Message | Merlin Moncure | 2009-05-09 17:24:20 | Re: limit-offset different result sets with same query |