Hello,
I think that conditional indexes not so clever as can.. Just little one
example:
isbs=# create unique index person_login on person (login) where
login<>'';
CREATE INDEX
isbs=# explain select * from person where login='user';
QUERY PLAN
-
On Wed, 25 Jun 2003 17:33:27 +0800
Ruslan A Dautkhanov <[EMAIL PROTECTED]> wrote:
> Postgres start to use conditional index only when I also pass index'
> condition:
> login='user' AND login<>'' ...
i belive it's pretty rational when you'll think that you can have your own operators
which d
Hubert Lubaczewski wrote:
On Wed, 25 Jun 2003 17:33:27 +0800
Ruslan A Dautkhanov <[EMAIL PROTECTED]> wrote:
Postgres start to use conditional index only when I also pass index'
condition:
login='user' AND login<>'' ...
i belive it's pretty rational when you'll think t
On Wed, 25 Jun 2003, Ruslan A Dautkhanov wrote:
Bugs is not the right place for this, -general would be better.
> I think that conditional indexes not so clever as can.. Just little one
> example:
>
> isbs=# create unique index person_login on person (login) where
> login<>'';
> CREATE IN
Stephan Szabo <[EMAIL PROTECTED]> writes:
> The system can recognize simple inequality implications, for example "x <
> 1" implies "x < 2"; otherwise the predicate condition must exactly match
> the query's WHERE condition or the index will not be recognized to be
> usable.
The reason it understan
The above-cited message appears to be virus spawn; beware of opening it
in Microsloth-written mail readers.
regards, tom lane
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://archive
