Re: query doesn't always follow 'correct' path..

From: Виктор Егоров <vyegorov(at)gmail(dot)com>
To: Bert <biertie(at)gmail(dot)com>
Cc: pgsql-sql <pgsql-sql(at)postgresql(dot)org>
Subject: Re: query doesn't always follow 'correct' path..
Date: 2013-02-18 15:20:15
Message-ID: CAGnEbojHAVeo6PRHdNTdn6244kdN+pm426s3beK3OcF_HUv=6g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-sql

2013/2/18 Bert <biertie(at)gmail(dot)com>

> When I don't touch the indexscan setting I get the following output:
> Total query runtime: 611484 ms.
> 20359 rows retrieved.
> and the following plan: http://explain.depesz.com/s/sDy
>
> However, when I put set enable_indexscan=off; in fron of the same query I
> get the following output:
> Total query runtime: 16281 ms.
> 20599 rows retrieved.
> and the followign plan: http://explain.depesz.com/s/EpP
>

Is this a typo or do you really get different number of rows returned with
and without indexscans?
Is this expected for the same query to return different sets over time?

--
Victor Y. Yegorov

In response to

Responses

Browse pgsql-sql by date

  From Date Subject
Next Message Julien Cigar 2013-02-18 15:20:51 Re: query doesn't always follow 'correct' path..
Previous Message Bert 2013-02-18 14:39:47 Re: query doesn't always follow 'correct' path..