"Ace" <[EMAIL PROTECTED]> writes:
> I've upgraded my DB to 7.3.1 from 7.2. The following update causes the SEQ
> SCAN instead of INDEX SCAN (in 7.2 there was no bug like that):
I don't believe that. No version of Postgres would have generated an
index scan on this query, because you've got a type
I've upgraded my DB to 7.3.1 from 7.2. The following update causes the SEQ
SCAN instead of INDEX SCAN (in 7.2 there was no bug like that):
create table machines(
i_sprzetx int,
mod char(10),
type char(30)
);
create table sprzetx(
rowid int,
ident char(50)
);
create index i_sprzetx on sprzet
