Re: Table access method not behaving like Oracle (index vs sequential scan). Examples and stats provided. - Mailing list pgsql-general

From Manfred Koizar
Subject Re: Table access method not behaving like Oracle (index vs sequential scan). Examples and stats provided.
Date
Msg-id 1lbki0tqhbf64oajjthfj5uhue3pe407ni@email.aon.at
Whole thread Raw
In response to Table access method not behaving like Oracle (index vs sequential scan). Examples and stats provided.  ("Kevin Macdonald" <nospam@please.thankyou>)
List pgsql-general
On Thu, 22 Jul 2004 04:34:26 GMT, "Kevin Macdonald"
<nospam@please.thankyou> wrote:
>(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)

No, Postgres always consults the heap to get the desired values.  The
most obvious reason is that visibility information is stored in heap
tuples but not in index tuples.

Servus
 Manfred

pgsql-general by date:

Previous
From: "A Palmblad"
Date:
Subject: Re: database troubles - various errors
Next
From: "Marc G. Fournier"
Date:
Subject: Re: Unsupported 3rd-party solutions (Was: Few questions