Re: [BUGS] General Bug Report: Bug in optimizer

From: Vadim Mikheev <vadim(at)krs(dot)ru>
To: Andriy I Pilipenko <bamby(at)marka(dot)net(dot)ua>
Cc: hackers(at)postgresql(dot)org
Subject: Re: [BUGS] General Bug Report: Bug in optimizer
Date: 1999-03-18 13:55:22
Message-ID: 36F105CA.5C068E40@krs.ru
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-hackers

Unprivileged user wrote:
>
> PostgreSQL version : 6.4.2
>
...
>
> Here is an example session. Note that in first SELECT
> backend uses index scan, and in second one it uses
> sequental scan.
>
> == cut ==
> bamby=> create table table1 (field1 int);
> CREATE
> bamby=> create index i_table1__field1 on table1 (field1);
> CREATE
> bamby=> explain select * from table1 where field1 = 1;
> NOTICE: QUERY PLAN:
>
> Index Scan using i_table1__field1 on table1 (cost=0.00 size=0 width=4)
^^^^^^
Hmmm... Seems that vacuum wasn't run for table1.
Why is index used ?!!!
It's bug!

> EXPLAIN
> bamby=> explain select * from table1 where field1 = -1;
> NOTICE: QUERY PLAN:
>
> Seq Scan on table1 (cost=0.00 size=0 width=4)

Run

vacuum table1

Vadim

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Andriy I Pilipenko 1999-03-18 15:22:14 Re: [BUGS] General Bug Report: Bug in optimizer
Previous Message Unprivileged user 1999-03-18 13:34:57 General Bug Report: Bug in optimizer

Browse pgsql-hackers by date

  From Date Subject
Next Message Zeugswetter Andreas IZ5 1999-03-18 15:21:54 AW: [HACKERS] "CANNOT EXTEND" -
Previous Message Unprivileged user 1999-03-18 13:34:57 General Bug Report: Bug in optimizer