| From: | Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | <stas-pgsql(at)xstas(dot)net>, <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Seq scan |
| Date: | 2002-08-16 17:20:32 |
| Message-ID: | 20020816101922.L99304-100000@megazone23.bigpanda.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Fri, 16 Aug 2002, Tom Lane wrote:
> Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com> writes:
> > On Fri, 16 Aug 2002 stas-pgsql(at)xstas(dot)net wrote:
> >> "SELECT my_field FROM my_table WHERE id=12168996" takes
> >> about half a minute ( 'id' is an sequential indexed field in my_table )
> >>
> >> EXPLAIN says it is doing a Seq Scan
>
> > Have you vacuum analyzed the table?
>
> I'm betting it's ye olde wrong-datatype issue. What's the data type of
> id? If it's not int4 then a cast is indicated ...
Well, he said that the "solution below did not help" in response to a
message about casting the data type, so I was wondering if it was simply
a default stats case.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bryan White | 2002-08-16 17:22:08 | query planner oddity for data constant vs current_date |
| Previous Message | Tom Lane | 2002-08-16 17:05:03 | Re: Seq scan |