Re: pg_index.isclustered can work - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: pg_index.isclustered can work
Date
Msg-id 200105151354.f4FDsd701285@candle.pha.pa.us
Whole thread Raw
In response to Re: pg_index.isclustered can work  (Hiroshi Inoue <Inoue@tpf.co.jp>)
List pgsql-hackers
[ Charset US-ASCII unsupported, converting... ]
> Bruce Momjian wrote:
> > 
> > > Bruce Momjian <pgman@candle.pha.pa.us> writes:
> 
> [snip]
> 
> > 
> > FYI, the reference to pg_index.indisclustered in ODBC was assuming it
> > meant it was a hash index,
> 
> Hmm where could I see it ?
> 
> > which is just plain wrong, so that code is
> > not coming back.
> > 

It is in info.c, SQLStatistics():
               /*                * Clustered index?  I think non-clustered should be type                * OTHER not
HASHED               */               set_tuplefield_int2(&row->tuple[6], (Int2) (atoi(isclustered) ?
SQL_INDEX_CLUSTERED: SQL_INDEX_OTHER));
 

The HASH mention has me confused.  Is that code valid?  Maybe so.  What
does ODBC think the column means, HASH or CLUSTER?

--  Bruce Momjian                        |  http://candle.pha.pa.us pgman@candle.pha.pa.us               |  (610)
853-3000+  If your life is a hard drive,     |  830 Blythe Avenue +  Christ can be your backup.        |  Drexel Hill,
Pennsylvania19026
 


pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: pg_index.indislossy
Next
From: Bruce Momjian
Date:
Subject: Re: optimiser problem