Re: 'Index Full Scan' for Index Scan without Index Cond - Mailing list pgsql-patches

From Simon Riggs
Subject Re: 'Index Full Scan' for Index Scan without Index Cond
Date
Msg-id 1149592794.2621.420.camel@localhost.localdomain
Whole thread Raw
In response to 'Index Full Scan' for Index Scan without Index Cond  (ITAGAKI Takahiro <itagaki.takahiro@oss.ntt.co.jp>)
Responses Re: 'Index Full Scan' for Index Scan without Index Cond  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-patches
On Tue, 2006-06-06 at 18:51 +0900, ITAGAKI Takahiro wrote:
> Indexes are used for two purpose, for selection and for ordering, but EXPLAIN
> shows them as 'Index Scan' in both cases. This patch changes EXPLAIN output of
> Index Scan without Index Cond to 'Index Full Scan'.

I like it.

Will that test always hold true? Even if it is currently true, perhaps
there should be a code comment to say we rely on that behaviour later to
make EXPLAIN function correctly? We definitely need some code comments
somewhere.

Perhaps we should call it 'Ordered Scan' so that it is completely
different from 'Index Scan'?

--
  Simon Riggs
  EnterpriseDB   http://www.enterprisedb.com


pgsql-patches by date:

Previous
From: ITAGAKI Takahiro
Date:
Subject: 'Index Full Scan' for Index Scan without Index Cond
Next
From: Simon Riggs
Date:
Subject: Re: table/index fillfactor control