Re: PG 7.4.3 optimizer choosing sequential scan. Why?

From: Greg Stark <gsstark(at)mit(dot)edu>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Re: PG 7.4.3 optimizer choosing sequential scan. Why?
Date: 2004-07-26 06:12:00
Message-ID: 87fz7fwb4f.fsf@stark.xeocode.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


Barry S <barry(at)nospam(dot)4(dot)me(dot)thx(dot)com> writes:

> > * The table contains one index: P1_NRN_ROAD_V (v, sobjid) (The index
> > includes the column sobjid because the query projects this col, and its
> > inclusion in the index allows it to be serviced without accessing the
> > underlying table)

(Unlike Oracle) Postgres *always* has to access the underlying table.

--
greg

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2004-07-26 06:17:10 Re: 7.5 release notes
Previous Message Tom Lane 2004-07-26 06:05:04 Re: 7.5 backend crash