Re: JOIN between three *simple* tables ...

From: "Marc G(dot) Fournier" <scrappy(at)hub(dot)org>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-sql(at)postgresql(dot)org, <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: JOIN between three *simple* tables ...
Date: 2002-02-06 21:41:17
Message-ID: 20020206174041.L57607-100000@earth.hub.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-sql


Okay, now I'm annoyed ... I *swear* I ran VACUUM ANALYZE a couple of times
since populating those tables *sigh* now its bringing up indices I'm
expecting :(

On Wed, 6 Feb 2002, Tom Lane wrote:

> "Marc G. Fournier" <scrappy(at)hub(dot)org> writes:
> > iwantu=# \d poc_uid
> > Index "poc_uid"
> > Column | Type
> > --------+--------
> > uid | bigint
> > btree
>
> > iwantu=# explain select count(1) from orientation_c poc where uid = 1;
> > NOTICE: QUERY PLAN:
>
> > Aggregate (cost=2264.97..2264.97 rows=1 width=0)
> > -> Seq Scan on orientation_c poc (cost=0.00..2264.96 rows=1 width=0)
>
> > EXPLAIN
>
> You're forgetting ye olde constant-casting problem. You need something
> like
>
> select count(1) from orientation_c poc where uid = 1::bigint;
>
> to use an index on a bigint column.
>
> Not sure about the other thing; have you VACUUM ANALYZEd (or at least
> ANALYZEd) since filling the tables? It looks like the system thinks
> the tables are much smaller than they really are.
>
> regards, tom lane
>

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2002-02-06 22:03:20 Re: Threaded PosgreSQL server
Previous Message Ian Harding 2002-02-06 21:39:50 Re: [Fwd: MS SQL compatible functions]

Browse pgsql-sql by date

  From Date Subject
Next Message Christopher Kings-Lynne 2002-02-07 00:46:09 type aliases in 7.0.3
Previous Message Tom Lane 2002-02-06 21:14:33 Re: JOIN between three *simple* tables ...