| From: | Pengzhou Tang <ptang(at)pivotal(dot)io> |
|---|---|
| To: | Jeff Davis <pgsql(at)j-davis(dot)com> |
| Cc: | Justin Pryzby <pryzby(at)telsasoft(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>, Melanie Plageman <melanieplageman(at)gmail(dot)com>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, Taylor Vesely <tvesely(at)pivotal(dot)io>, Adam Lee <ali(at)pivotal(dot)io>, Melanie Plageman <mplageman(at)pivotal(dot)io>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Memory-Bounded Hash Aggregation |
| Date: | 2020-03-20 05:26:43 |
| Message-ID: | CAG4reAQ_852vigJ2cvaSQEQEstyOp5gPafS6pJrUKd4wzf_2Wg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Mar 20, 2020 at 1:20 PM Pengzhou Tang <ptang(at)pivotal(dot)io> wrote:
> Hi,
>
> I happen to notice that "set enable_sort to false" cannot guarantee the
> planner to use hashagg in test groupingsets.sql,
> the following comparing results of sortagg and hashagg seems to have no
> meaning.
>
>
Please forget my comment, I should set enable_groupingsets_hash_disk too.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Kapila | 2020-03-20 05:54:25 | Re: error context for vacuum to include block number |
| Previous Message | Paul A Jungwirth | 2020-03-20 05:24:53 | Re: range_agg |