Postgres Pro
Downloads
Home   >   mailing lists

Re: query doesn't always follow 'correct' path.. - Mailing list pgsql-sql

From Виктор Егоров
Subject Re: query doesn't always follow 'correct' path..
Date
Msg-id CAGnEbojHAVeo6PRHdNTdn6244kdN+pm426s3beK3OcF_HUv=6g@mail.gmail.com
Whole thread Raw
In response to query doesn't always follow 'correct' path..  (Bert <biertie@gmail.com>)
Responses Re: query doesn't always follow 'correct' path..
List pgsql-sql
Tree view
2013/2/18 Bert <biertie@gmail.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

pgsql-sql by date:

Previous
From: Bert
Date:
Subject: Re: query doesn't always follow 'correct' path..
Next
From: Julien Cigar
Date:
Subject: Re: query doesn't always follow 'correct' path..