| From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pg_index.isclustered can work |
| Date: | 2001-05-15 14:34:51 |
| Message-ID: | 200105151434.f4FEYph03794@candle.pha.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
[ Charset US-ASCII unsupported, converting... ]
> Bruce Momjian wrote:
> >
> > > Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)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(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Vince Vielhaber | 2001-05-15 14:40:41 | I know there are few hams on this list... |
| Previous Message | Jean-Arthur Silve | 2001-05-15 14:17:22 | Not a PG question: SCSI question |