| From: | Joe Conway <mail(at)joeconway(dot)com> |
|---|---|
| To: | ow <oneway_111(at)yahoo(dot)com> |
| Cc: | jasiek <jasiek(at)klaster(dot)net>, pgsql-sql(at)postgresql(dot)org |
| Subject: | Re: Seq Scans when index expected to be used |
| Date: | 2003-11-29 18:25:58 |
| Message-ID: | 3FC8E4B6.8030901@joeconway.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
ow wrote:
> My impression was that the index "I_bca" covers the query, hence there should
> not be a need to go to the table itself. Why would it?
Postgres always has to go to the table. The ability to read data
directly from indexes (ala other RDBMSs) has been discussed, but not
implemented. IIRC it's a hard problem due to the way Postgres does MVCC.
Check the archives.
> explain analyze vs explain. Normally, would've used "explain analyze" but in
> this case it's taking way too long so I used "explain".
I can understand that, but most people will ask for explain analyze
anyway ;-)
Joe
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jamie Lawrence | 2003-11-29 19:34:20 | Re: Updating session id based on accesstimeout |
| Previous Message | Andreas Heissenberger | 2003-11-29 18:18:46 | Updating session id based on accesstimeout |