pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Thomas Swan <tswan@idigx.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: scott.marlowe <scott.marlowe@ihs.com>
Cc: Neil Conway <neilc@samurai.com>
Cc: Pailloncy Jean-Gérard <pailloncy@ifrance.com>
Cc: PostgreSQL Performance <pgsql-performance@postgresql.org>
Subject: Re: slow plan for min/max
Date: Tue, 09 Sep 2003 14:06:56 -0500
Message-ID: <3F5E24D0.4040309@idigx.com> (raw)
In-Reply-To: <3303.1063056376@sss.pgh.pa.us>
References: <Pine.LNX.4.33.0309081434150.11709-100000@css120.ihs.com>
	<3303.1063056376@sss.pgh.pa.us>

Tom Lane wrote:

>"scott.marlowe" <scott.marlowe@ihs.com> writes:
>  
>
>>On Mon, 8 Sep 2003, Neil Conway wrote:
>>    
>>
>>>As was pointed out in a thread a couple days ago, MIN/MAX() optimization
>>>has absolutely nothing to do with MVCC. It does, however, make
>>>optimizing COUNT() more difficult.
>>>      
>>>
>
>  
>
>>Not exactly.  While max(id) is easily optimized by query replacement, 
>>more complex aggregates will still have perfomance issues that would not 
>>be present in a row locking database.  i.e. max((field1/field2)*field3) is 
>>still going to cost more to process, isn't it?
>>    
>>
>
>Er, what makes you think that would be cheap in any database?
>
>Postgres would actually have an advantage given its support for
>expressional indexes (nee functional indexes).  If we had an optimizer
>transform to convert MAX() into an index scan, I would expect it to be
>able to match up max((field1/field2)*field3) with an index on
>((field1/field2)*field3).
>  
>

Would it be possible to rewrite min and max at the parser level into a
select/subselect  (clause) condition ( repeat condition ) order by
(clause ) descending/ascending limit 1 and thereby avoiding the
penalties of altering the default aggregate behavior?  Would it yield
anything beneficial?





view thread (20+ messages)  latest in thread

Message-ID: <3F5E24D0.4040309@idigx.com>
Permalink:  ../3F5E24D0.4040309@idigx.com/
Also on:    postgresql.org/message-id/3F5E24D0.4040309@idigx.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-performance@postgresql.org
  Cc: tswan@idigx.com, tgl@sss.pgh.pa.us, scott.marlowe@ihs.com, neilc@samurai.com, pailloncy@ifrance.com
  Subject: Re: slow plan for min/max
  In-Reply-To: <3F5E24D0.4040309@idigx.com>
  References: <Pine.LNX.4.33.0309081434150.11709-100000@css120.ihs.com> <3303.1063056376@sss.pgh.pa.us> <3F5E24D0.4040309@idigx.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox