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

From: Amit Langote <amitlangote09(at)gmail(dot)com>
To: Sergey Konoplev <gray(dot)ru(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:13:33
Message-ID: CA+HiwqH9atqnDeR6V5L-9eXchiwyy-TM6fvKQTmDc+BVSZyT2w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

>> 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 you set enable_xxx=off, it not actually disables the xxx
> operation, it sets the start cost to the high value (10000000000).
>

Oh, okay, thanks!

--
Amit Langote

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Amit Langote 2013-05-27 08:15:26 Re: Seq Scan cost shown to be (cost=10000000000.00..10000000001.10)
Previous Message Victor Yegorov 2013-05-27 08:04:21 Re: Seq Scan cost shown to be (cost=10000000000.00..10000000001.10)