Robert Haas wrote:
> The advice in Stephen's email is also very good - in particular,
> whatever you come up with, you should submit performance results.
> Note that while --enable-profiling is very useful and profiling
> numbers are good to submit, you'll also want to make sure you do a
> build that is optimized for speed (i.e. no profiling, no casserts, no
> debug) and do timings on that.
I'm particularly interested to see how much the patch hurts performance
in the cases where it's not helping.
-- Heikki Linnakangas EnterpriseDB http://www.enterprisedb.com