Regarding Plan tree output(Index/Bitmap Scan) - Mailing list pgsql-hackers

From Ajay P S
Subject Regarding Plan tree output(Index/Bitmap Scan)
Date
Msg-id CAHjjAw17pXwqGQfZeGF24rucDmvW2UqmRoRgtibwQJUfkOA23A@mail.gmail.com
Whole thread Raw
Responses Re: Regarding Plan tree output(Index/Bitmap Scan)  (Justin Pryzby <pryzby@telsasoft.com>)
List pgsql-hackers
Hi,

I am trying to understand the Plan tree for select queries. Can you
please help me with the below queries?

1) Why is there a difference in plan tree for these two queries? User
table tidx1 has an index on column 'a' .
2) Why do we do Index scan and not  Bitmap Index Scan for catalog tables?

postgres=# explain select * from pg_class where oid=2051;
                                     QUERY PLAN
-------------------------------------------------------------------------------------
 Index Scan using pg_class_oid_index on pg_class  (cost=0.27..8.29
rows=1 width=265)
   Index Cond: (oid = '2051'::oid)
(2 rows)

postgres=# explain select * from tidx1 where a=1;
                             QUERY PLAN
--------------------------------------------------------------------
 Bitmap Heap Scan on tidx1  (cost=4.24..14.91 rows=11 width=8)
   Recheck Cond: (a = 1)
   ->  Bitmap Index Scan on idx1  (cost=0.00..4.24 rows=11 width=0)
         Index Cond: (a = 1)
(4 rows)

postgres=# select * from tidx1;
 a | b
---+---
 1 | 2
 2 | 2
 3 | 2
 4 | 2
 5 | 2
(5 rows)

Best,
Aj



pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: Add LZ4 compression in pg_dump
Next
From: Stephen Frost
Date:
Subject: Re: longfin missing gssapi_ext.h