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

From: Manfred Koizar <mkoi-pg(at)aon(dot)at>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: Table access method not behaving like Oracle (index vs sequential scan). Examples and stats provided.
Date: 2004-08-23 17:57:01
Message-ID: 1lbki0tqhbf64oajjthfj5uhue3pe407ni@email.aon.at
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Thu, 22 Jul 2004 04:34:26 GMT, "Kevin Macdonald"
<nospam(at)please(dot)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

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Marc G. Fournier 2004-08-23 18:35:32 Re: Unsupported 3rd-party solutions (Was: Few questions
Previous Message A Palmblad 2004-08-23 17:51:21 Re: database troubles - various errors