Re: pg_index.isclustered can work
От | Bruce Momjian |
---|---|
Тема | Re: pg_index.isclustered can work |
Дата | |
Msg-id | 200105151434.f4FEYph03794@candle.pha.pa.us обсуждение исходный текст |
Ответ на | Re: pg_index.isclustered can work (Hiroshi Inoue <Inoue@tpf.co.jp>) |
Список | 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. > > I now think the original ODBC code was right. It has defined as possible values:#define SQL_TABLE_STAT 0#define SQL_INDEX_CLUSTERED 1#define SQL_INDEX_HASHED 2#define SQL_INDEX_OTHER 3 Not sure what SQL_TABLE_STAT is for, perhaps we should flag for pg_statistics? Anyway, the test of the flag looks correct to me. Why they would care only about HASH and CLUSTERED, I don't know. I will restore the code, and fix the HASH while I am at it. Of course, the cluster field is still alway false, but it will be ready if we ever get it working. -- 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 по дате отправления: