On Fri, Jun 24, 2005 at 11:23:54AM +0100, Richard Huxton wrote:
> >I qouted them to use indexes. The other method is type casting the
> >values to indexed column type. I prefer the quoting method.
>
> Sorry - this is just plain wrong.
>
> If you had an int8 column and a value such as 17, then PG
Sezai YILMAZ wrote:
Richard Huxton wrote:
OK - all very simple. And you've said there are about 580,000 rows.
test=> explain analyze select id,name from person where id in
('17201', '338191', '244319', '515209', '20415');
Why are you quoting integers?
I qouted them to use indexes. The oth
Richard Huxton wrote:
Sezai YILMAZ wrote:
Hello!
I have a table eith name person as described below. It has an unique
index for id column (it is also primary key) and has an index for
parent column.
If I run a query with where clause on id column it uses the index
(look at the first expl
On Fri, Jun 24, 2005 at 11:44:50AM +0300, Sezai YILMAZ wrote:
> Hello!
>
> I have a table eith name person as described below. It has an unique
> index for id column (it is also primary key) and has an index for parent
> column.
> Why the difference of both queries is so dramatical for unique
Sezai YILMAZ wrote:
Hello!
I have a table eith name person as described below. It has an unique
index for id column (it is also primary key) and has an index for parent
column.
If I run a query with where clause on id column it uses the index (look
at the first explain analyze result; it sa
Hello!
I have a table eith name person as described below. It has an unique
index for id column (it is also primary key) and has an index for parent
column.
If I run a query with where clause on id column it uses the index (look
at the first explain analyze result; it says "Index Scan using.
