From: | Emanuel Calvo Franco <postgres(dot)arg(at)gmail(dot)com> |
---|---|
To: | David Fetter <david(at)fetter(dot)org> |
Cc: | postgresql Forums <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: limit-offset different result sets with same query |
Date: | 2009-05-08 21:40:33 |
Message-ID: | f205bb120905081440k7912980ak7b15fc52f59d0ff8@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
2009/5/8 David Fetter <david(at)fetter(dot)org>:
> On Fri, May 08, 2009 at 06:10:18PM -0300, Emanuel Calvo Franco wrote:
>> Hi all.
>>
>> I'll make this faster.
>>
>> I hace this table and this function:
>
> You should only ever assume that your SELECT's output will have a
> particular ordering when you include an ORDER BY clause that actually
> specifies the order well enough :)
>
I test it in the first time :)
With the 'order by' it works well, but in 'theory' if you
run sequentially and physically a table, you expect obtain the same
results with a same query.
There is no indexes that can intersect the results or inherits
tables.
But with the option synchronize_seqscans in off, it works like
i expected :)
i will study a bit more this option on monday (like always).
--
Emanuel Calvo Franco
Sumate al ARPUG !
( www.arpug.com.ar)
ArPUG / AOSUG Member
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2009-05-08 21:40:48 | Re: limit-offset different result sets with same query |
Previous Message | Adam Rich | 2009-05-08 21:36:10 | Re: limit-offset different result sets with same query |