Re: slow plan for min/max - Mailing list pgsql-performance

From Matt Clark
Subject Re: slow plan for min/max
Date
Msg-id LFEIJBEOKGPDHCEMDGNFIEGHCAAA.matt@ymogen.net
Whole thread Raw
In response to Re: slow plan for min/max  ("Matt Clark" <matt@ymogen.net>)
List 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?


pgsql-performance by date:

Previous
From: "Matt Clark"
Date:
Subject: Re: slow plan for min/max
Next
From: Tom Lane
Date:
Subject: Re: slow plan for min/max