Re: PG 7.4.3 optimizer choosing sequential scan. Why? - Mailing list pgsql-hackers

From Greg Stark
Subject Re: PG 7.4.3 optimizer choosing sequential scan. Why?
Date
Msg-id 87fz7fwb4f.fsf@stark.xeocode.com
Whole thread Raw
In response to Re: PG 7.4.3 optimizer choosing sequential scan. Why?  (Barry S <barry@nospam.4.me.thx.com>)
List pgsql-hackers
Barry S <barry@nospam.4.me.thx.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



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: 7.5 backend crash
Next
From: Tom Lane
Date:
Subject: Re: 7.5 release notes