From: | Jeff Davis <pgsql(at)j-davis(dot)com> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Default setting for enable_hashagg_disk |
Date: | 2020-04-07 18:20:46 |
Message-ID: | 9d9d1e1252a52ea1bad84ea40dbebfd54e672a0f.camel@j-davis.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs pgsql-hackers |
This is just a placeholder thread for an open item that I'm adding to
the Open Items list. We can make a decision later.
Now that we have Disk-based Hash Aggregation, there are a lot more
situations where the planner can choose HashAgg. The
enable_hashagg_disk GUC, if set to true, chooses HashAgg based on
costing. If false, it only generates a HashAgg path if it thinks it
will fit in work_mem, similar to the old behavior (though it wlil now
spill to disk if the planner was wrong about it fitting in work_mem).
The current default is true.
I expect this to be a win in a lot of cases, obviously. But as with any
planner change, it will be wrong sometimes. We may want to be
conservative and set the default to false depending on the experience
during beta. I'm inclined to leave it as true for now though, because
that will give us better information upon which to base any decision.
Regards,
Jeff Davis
From | Date | Subject | |
---|---|---|---|
Next Message | Justin Pryzby | 2020-04-07 22:39:01 | Re: Default setting for enable_hashagg_disk |
Previous Message | David G. Johnston | 2020-04-06 15:21:01 | Re: Proposal to improve the content in subsection 8.16.6. "Composite Type Input and Output Syntax" |
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2020-04-07 18:28:09 | Re: Improving connection scalability: GetSnapshotData() |
Previous Message | Ashwin Agrawal | 2020-04-07 18:01:55 | Re: SyncRepLock acquired exclusively in default configuration |