Re: slow plan for min/max

From: "Matt Clark" <matt(at)ymogen(dot)net>
To: "scott(dot)marlowe" <scott(dot)marlowe(at)ihs(dot)com>
Cc: <pgsql-performance(at)postgresql(dot)org>
Subject: Re: slow plan for min/max
Date: 2003-09-08 23:38:36
Message-ID: LFEIJBEOKGPDHCEMDGNFIEGHCAAA.matt@ymogen.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

> Actually, referring down to later parts of this thread, why can't this
> optimisation be performed internally for built-in types? I understand the
> issue with aggregates over user-defined types, but surely optimising max()
> for int4, text, etc is safe and easy?

Sorry, missed the bit about user-defined functions. So I should have said
built-in functions operating over built-in types. Which does sound more
complicated, but anyone redefining max() is surely not in a position to seek
sympathy if they lose performance?

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message Tom Lane 2003-09-08 23:42:31 Re: slow plan for min/max
Previous Message Matt Clark 2003-09-08 23:17:09 Re: slow plan for min/max