Is this a planner bug?

From: Torsten Förtsch <torsten(dot)foertsch(at)gmx(dot)net>
To: pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Is this a planner bug?
Date: 2014-04-22 12:10:19
Message-ID: 53565C2B.7040000@gmx.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Hi,

I got this plan:

Limit (cost=0.00..1.12 rows=1 width=0)
-> Seq Scan on fmb (cost=0.00..6964734.35 rows=6237993 width=0)
Filter: ...

The table has ~80,000,000 rows. So, the filter, according to the plan,
filters out >90% of the rows. Although the cost for the first row to
come out of the seqscan might be 0, the cost for the first row to pass
the filter and, hence, to hit the limit node is probably higher.

Thanks,
Torsten

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Albe Laurenz 2014-04-22 12:16:26 Re: How to ignore blank lines with file_fdw
Previous Message Tim Kane 2014-04-22 12:01:38 hstore binary representation of keys