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

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 (view raw or flat)
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

pgsql-performance by date

Next:From: Tom LaneDate: 2003-09-08 23:42:31
Subject: Re: slow plan for min/max
Previous:From: Matt ClarkDate: 2003-09-08 23:17:09
Subject: Re: slow plan for min/max

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