Tom Lane wrote: > Log message: > Finish implementation of hashed aggregation. Add enable_hashagg GUC > parameter to allow it to be forced off for comparison purposes. > Add ORDER BY clauses to a bunch of regression test queries that will > otherwise produce randomly-ordered output in the new regime.
Tom, do we really want to add a GUC that is used just for comparison of performance? I know we have the seqscan on/off, but there are valid reasons to do that. Do you think there will be cases where it will faster to have this hash setting off? -- Bruce Momjian | http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square, Pennsylvania 19073 ---------------------------(end of broadcast)--------------------------- TIP 6: Have you searched our list archives? http://archives.postgresql.org
