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

From: Victor Yegorov <vyegorov(at)gmail(dot)com>
To: Amit Langote <amitlangote09(at)gmail(dot)com>
Cc: Postgres General <pgsql-general(at)postgresql(dot)org>
Subject: Re: Seq Scan cost shown to be (cost=10000000000.00..10000000001.10)
Date: 2013-05-27 08:04:21
Message-ID: CAGnEboiSB6bsdVUfPOJjf0+Rczgrd+H-i5V-Q5aiGC4ayi8CDg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

2013/5/27 Amit Langote <amitlangote09(at)gmail(dot)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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Amit Langote 2013-05-27 08:13:33 Re: Seq Scan cost shown to be (cost=10000000000.00..10000000001.10)
Previous Message Sergey Konoplev 2013-05-27 07:58:17 Re: Seq Scan cost shown to be (cost=10000000000.00..10000000001.10)