Skip site navigation (1) Skip section navigation (2)

Re: select slow?

From: "Jaime Casanova" <el_vigia_ec(at)hotmail(dot)com>
To: pgsql-performance(at)postgresql(dot)org
Subject: Re: select slow?
Date: 2004-03-31 14:27:50
Message-ID: BAY8-F7R0ZJi4W8StO00001d4b4@hotmail.com (view raw or flat)
Thread:
Lists: pgsql-performance
>
>On Tuesday 30 March 2004 20:25, Jaime Casanova wrote:
>>hi all,
> >
> >
> > i have an amd athlon with 256 ram (i know, this is not a *real* server 
>but
> > my tables are small)

>Nothing wrong with it - it's what I still use as my development server.
>
> > i'm using vb6 (win98) with pgsql-7.3.4 (rh8) trough the psqlodbc.
> >
> > when i do a select in took long to execute, here is an example
>
> > CREATE TABLE ICC_M_BANCO (
> >        CodBanco             SMALLINT NOT NULL,

> > select * from icc_m_banco where codbanco = 1;
> >
> > it tooks 13s from it's send until it's executed.
>
>Try:
>   SELECT * FROM icc_m_banco WHERE codbanco = 1::smallint;
>
>By default, PG will treat a numeric constant as integer not smallint, so 
>when
>it looks for an index it can't find one for integer, so scans instead.
>
>--
>   Richard Huxton
>   Archonet Ltd

There are no indexes yet, and the table is just 6 rows long so even if 
indexes exists the planner will do a seq scan. that's my whole point 63m for 
seq scan in 6 rows table is too much.

_________________________________________________________________
The new MSN 8: smart spam protection and 2 months FREE*  
http://join.msn.com/?page=features/junkmail


Responses

pgsql-performance by date

Next:From: Tom LaneDate: 2004-03-31 15:40:21
Subject: Re: select slow?
Previous:From: Richard HuxtonDate: 2004-03-31 12:07:54
Subject: Re: What index for 'like (%keyword%)' ???

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group