pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Chris Ruprecht <chrup999@yahoo.com>
To: pgsql <pgsql-sql@postgresql.org>
Subject: Re: Big table - using wrong index - why?
Date: Mon, 30 Jul 2001 13:54:18 -0500
Message-ID: <00b501c11929$096a4ec0$5dd26383@corp.compucom.com> (raw)
References: <006401c11913$9a563ae0$5dd26383@corp.compucom.com>
	<01d501c11916$b81603f0$48d210ac@jecw2k1>

Hi Joe,

I found the problem - it was a typical "aaaarrrgggghhh" - error. Since pseq
is declared int8, I need to say

select * from phonelog where entity = '001' and pseq >= 9120::int8 and pseq
<= 9123::int8;

(casting the two numbers). Then, it works like a charm ...

Best regards,
Chris



----- Original Message -----
From: "Joe Conway" <joseph.conway@home.com>
To: "Chris Ruprecht" <chrup999@yahoo.com>; "pgsql"
<pgsql-sql@postgresql.org>
Sent: Monday, July 30, 2001 11:43 AM
Subject: Re: [SQL] Big table - using wrong index - why?


> > phones=# \d i_pl_pseq
> >         Index "i_pl_pseq"
> >  Attribute |         Type
> > -----------+----------------------
> >  entity    | character varying(3)
> >  pseq      | bigint
> > btree
> >
> > phones=# explain select * from phonelog where entity = '001' and pseq >=
> > 9120 and pseq <= 9123;
> > NOTICE:  QUERY PLAN:
> >
> > Index Scan using i_pl_loadtimestamp on phonelog  (cost=0.00..209247.39
> > rows=607 width=137)
> >
> > EXPLAIN
> >
> > phones=# \d i_pl_loadtimestamp
> >     Index "i_pl_loadtimestamp"
> >  Attribute |         Type
> > -----------+----------------------
> >  entity    | character varying(3)
> >  loaddate  | date
> >  loadtime  | time
> > btree
>
> Just a guess, but what happens if you build i_pl_pseq(pseq, entity), i.e.
> reverse the key fields? Also, has the table been vacuum analyzed?
>
> -- Joe
>
>
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Don't 'kill -9' the postmaster


_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com




view thread (4+ messages)  latest in thread

Message-ID: <00b501c11929$096a4ec0$5dd26383@corp.compucom.com>
Permalink:  ../00b501c11929$096a4ec0$5dd26383@corp.compucom.com/
Also on:    postgresql.org/message-id/00b501c11929$096a4ec0$5dd26383@corp.compucom.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-sql@postgresql.org
  Cc: chrup999@yahoo.com
  Subject: Re: Big table - using wrong index - why?
  In-Reply-To: <00b501c11929$096a4ec0$5dd26383@corp.compucom.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox