On Wed, Oct 19, 2016 at 8:54 AM, negora <pub...@negora.com> wrote:

>     Nested Loop  (cost=245.92..383723.28 rows=7109606 width=38) (actual
> time=1.091..2616.553 rows=8906075 loops=1)
>

I wonder about the use-case for this query, because it returns more than 8M
rows, so 2.6 seconds that sounds that much for so many rows. Is it for an
end user application? Isn't there any kind of pagination?


-- 
Matheus de Oliveira

Reply via email to