From: | Laurent Laborde <kerdezixe(at)gmail(dot)com> |
---|---|
To: | Greg Stark <gsstark(at)mit(dot)edu> |
Cc: | PostgreSQL Performance <pgsql-performance(at)postgresql(dot)org> |
Subject: | Re: Cost of sort/order by not estimated by the query planner |
Date: | 2009-12-02 12:47:16 |
Message-ID: | 8a1bfe660912020447x11c4e77nd7095a422ff0af85@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-performance |
On Wed, Dec 2, 2009 at 1:42 PM, Greg Stark <gsstark(at)mit(dot)edu> wrote:
> On Wed, Dec 2, 2009 at 11:13 AM, Laurent Laborde <kerdezixe(at)gmail(dot)com> wrote:
>>> QUERY PLAN
>>> -----------------------------------------------------------------------------------------------------
>>> Limit (cost=66114.13..66115.38 rows=500 width=1114)
>>> -> Sort (cost=66114.13..66157.37 rows=17296 width=1114)
>>> Sort Key: id
>>> -> Bitmap Heap Scan on _article (cost=138.32..65252.29
>>> rows=17296 width=1114)
>>> Recheck Cond: (bitfield && B'1'::bit varying)
>>> -> Bitmap Index Scan on idx_article_bitfield
>>> (cost=0.00..134.00 rows=17296 width=0)
>>> Index Cond: (bitfield && B'1'::bit varying)
>
>
> Uhm, what kind of index is idx_article_bitfield?
Mmm, i forgot about that ! It's in a GIN index.
"idx_article_bitfield" gin (bitfield), tablespace "indexspace"
--
Laurent "ker2x" Laborde
Sysadmin & DBA at http://www.over-blog.com/
From | Date | Subject | |
---|---|---|---|
Next Message | Greg Stark | 2009-12-02 12:47:31 | Re: Cost of sort/order by not estimated by the query planner |
Previous Message | Greg Stark | 2009-12-02 12:42:16 | Re: Cost of sort/order by not estimated by the query planner |
From | Date | Subject | |
---|---|---|---|
Next Message | Greg Stark | 2009-12-02 12:47:31 | Re: Cost of sort/order by not estimated by the query planner |
Previous Message | Greg Stark | 2009-12-02 12:42:16 | Re: Cost of sort/order by not estimated by the query planner |