Re: query doesn't always follow 'correct' path..
| От | Bert |
|---|---|
| Тема | Re: query doesn't always follow 'correct' path.. |
| Дата | |
| Msg-id | CAFCtE1kgqV8n7mb6dWk4HHv6psAxu4H5-xmkhKrzaFDwDqks1g@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: query doesn't always follow 'correct' path.. (Виктор Егоров <vyegorov@gmail.com>) |
| Список | pgsql-sql |
Hello,
there were 3 hours in between the 2 queries. so I guess new data was loaded already. new data is being loaded with that etl_run_id. wkr,
Bert
On Mon, Feb 18, 2013 at 4:20 PM, Виктор Егоров <vyegorov@gmail.com> wrote:
2013/2/18 Bert <biertie@gmail.com>Is this a typo or do you really get different number of rows returned with and without indexscans?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/sDyHowever, 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/EpPIs this expected for the same query to return different sets over time?--
Victor Y. Yegorov
--
Bert Desmet
0477/305361
В списке pgsql-sql по дате отправления: