Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: Poor performance on seq scan
- From: Markus Schaber <schabi(at)logix-tt(dot)com>
- To: pgsql-performance(at)postgresql(dot)org
- Subject: Re: Poor performance on seq scan
- Date: Mon, 18 Sep 2006 10:22:00 +0200
- Message-id: <450E5728(dot)7000802(at)logix-tt(dot)com>
Hi, Piotr, Piotr Kołaczkowski wrote: > Why match rows from the heap if ALL required data are in the index itself? > Why look at the heap at all? Because the index does not contain any transaction informations, so it has to look to the heap to find out which of the rows are current. This is one of the more debated points in the PostgreSQL way of MVCC implementation. Markus -- Markus Schaber | Logical Tracking&Tracing International AG Dipl. Inf. | Software Development GIS Fight against software patents in Europe! www.ffii.org www.nosoftwarepatents.org
- References:
- Poor performance on seq scan
- From: Laszlo Nagy
- Re: Poor performance on seq scan
- From: Heikki Linnakangas
- Re: Poor performance on seq scan
- From: Piotr Kołaczkowski
- Poor performance on seq scan
- Prev by Date: Re: Optimize SQL
- Next by Date: Re: Poor performance on seq scan
- Previous by thread: Re: Poor performance on seq scan
- Next by thread: Re: Poor performance on seq scan
- Indexes: