Skip site navigation (1) Skip section navigation (2)

Re: Index scan startup time

From: Markus Schaber <schabi(at)logix-tt(dot)com>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: pgsql-performance(at)postgresql(dot)org,Michael Stone <mstone+postgres(at)mathom(dot)us>
Subject: Re: Index scan startup time
Date: 2006-03-30 12:35:53
Message-ID: 442BD0A9.8050805@logix-tt.com (view raw or flat)
Thread:
Lists: pgsql-performance
Hi, Peter,

Peter Eisentraut wrote:
>>>The table has seen VACUUM FULL and REINDEX before this.
>>But no analyze?
> ANALYZE as well, but the plan choice is not the point anyway.

Maybe you could add a combined Index on activity_id and state, or (if
you use this kind of query more often) a conditional index on
activity_id where state in (10000,10001).

Btw, PostgreSQL 8.1 could AND two bitmap index scans on the activity and
state indices, and get the result faster (i presume).

Markus
-- 
Markus Schaber | Logical Tracking&Tracing International AG
Dipl. Inf.     | Software Development GIS

Fight against software patents in EU! www.ffii.org www.nosoftwarepatents.org

In response to

pgsql-performance by date

Next:From: Michael StoneDate: 2006-03-30 12:42:53
Subject: Re: Index scan startup time
Previous:From: Steinar H. GundersonDate: 2006-03-30 12:31:34
Subject: Re: Index scan startup time

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group