From: | "Zeugswetter Andreas SB SD" <ZeugswetterA(at)spardat(dot)at> |
---|---|
To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Tatsuo Ishii" <t-ishii(at)sra(dot)co(dot)jp> |
Cc: | <pgsql-hackers(at)postgresql(dot)org> |
Subject: | AW: partial index |
Date: | 2001-08-06 07:29:10 |
Message-ID: | 46C15C39FEB2C44BA555E356FBCD6FA41EB36D@m0114.s-mxs.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp> writes:
> > test=# create index myindex on accounts(aid) where bid <> 0;
Hmm ? Am I reading correctly ? a restriction that is on a field, that
is not in the index ? Does that make sense ? (aid --> bid)
> The original implementation would have refused to let you create a
> partial index with such a WHERE clause, since <> isn't a
btree-indexable
> operator.
But that is sad, since it would be a rather important use. Couldn't it
be
rewritten to: (aid < 0 or aid > 0) ? (I assume you meant aid)
Andreas
From | Date | Subject | |
---|---|---|---|
Next Message | Turbo Fredriksson | 2001-08-06 07:29:34 | Re: PL/pgSQL: Return multiple rows |
Previous Message | Hiroshi Inoue | 2001-08-06 07:19:19 | Re: Possible solution for LIKE optimization |