Re: Seq Scan cost shown to be (cost=10000000000.00..10000000001.10)

Поиск
Список
Период
Сортировка
От Victor Yegorov
Тема Re: Seq Scan cost shown to be (cost=10000000000.00..10000000001.10)
Дата
Msg-id CAGnEboiSB6bsdVUfPOJjf0+Rczgrd+H-i5V-Q5aiGC4ayi8CDg@mail.gmail.com
обсуждение исходный текст
Ответ на Seq Scan cost shown to be (cost=10000000000.00..10000000001.10)  (Amit Langote <amitlangote09@gmail.com>)
Ответы Re: Seq Scan cost shown to be (cost=10000000000.00..10000000001.10)  (Amit Langote <amitlangote09@gmail.com>)
Список pgsql-general
Дерево обсуждения

2013/5/27 Amit Langote <amitlangote09@gmail.com>
Although, I suspect the (dropped index + enable_seqscan) causes this,
is the cost shown in explain output some kind of default max or
something like that for such abnormal cases?

When one uses “enable_” settings to adjust planner behavior, PostgreSQL
just sets really high costs for the operations affected (like the one you see).

As SeqScan is the only possible way to execute your query, it is still choosen.

Somewhat related thread: http://www.postgresql.org/message-id/4D5B06AC.2020700@lelarge.info


--
Victor Y. Yegorov

В списке pgsql-general по дате отправления:

Предыдущее
От: Sergey Konoplev
Дата:
Сообщение: Re: Seq Scan cost shown to be (cost=10000000000.00..10000000001.10)
Следующее
От: Amit Langote
Дата:
Сообщение: Re: Seq Scan cost shown to be (cost=10000000000.00..10000000001.10)