Message-ID: <3DAE0883.6090709@heart.com.au>
Date: Thu, 17 Oct 2002 10:46:59 +1000
From: Keith Gray <keith@heart.com.au>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:0.9.4.1) Gecko/20020508 Netscape6/6.2.3
MIME-Version: 1.0
To: Richard Huxton <dev@archonet.com>
Cc: PostgreSQL Mailing List <pgsql-sql@postgresql.org>
Subject: Re: Slow performance on MAX(primary_key)
References: <20021015071628.57518.qmail@web80304.mail.yahoo.com>
	<3DABC801.8060902@heart.com.au>
	<200210150923.15822.dev@archonet.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Richard Huxton wrote:

>>>  As of now, Max() doesn't utilizes the indices hence
>>>it always do a sequential scan.


>>Is this likely to be sorted in 7.2 ?
>>Is anyone looking at this?


> As I understand, the problem is that the optimisation only applies for simple 
> cases...


Getting MIN() adn MAX() seems fairly trivial to me.

When is on an index or more importantly Primary
Key it must be a common SQL.

Would it be possible in the code to look at
the field in MIN() or MAX() and if it is
indexed use a similar method to the suggested
SQL work around?

Can I help this to happen?


-- 

Keith Gray
Technical Services Manager
Heart Consulting Services