Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly
Appearance settings

Commit f36e820

Browse filesBrowse files
petergeogheganpetergeoghegan
committed
Doc: Remove obsolete CREATE AGGREGATE note.
The planner is in fact willing to use hash aggregation when work_mem is not set high enough for everything to fit in memory. This has been the case since commit 1f39bce, which added disk-based hash aggregation. There are a few remaining cases in which hash aggregation is avoided as a matter of policy when the planner surmises that spilling will be necessary. For example, callers of choose_hashed_setop() still conservatively avoid hash aggregation when spilling is anticipated. That doesn't seem like a good enough reason to mention hash aggregation in this context. Backpatch: 13-, where disk-based hash aggregation was introduced.
1 parent 0e3e1c4 commit f36e820
Copy full SHA for f36e820

File tree

Expand file treeCollapse file tree

1 file changed

+1
-4
lines changed
Filter options
Expand file treeCollapse file tree

1 file changed

+1
-4
lines changed

‎doc/src/sgml/ref/create_aggregate.sgml

Copy file name to clipboardExpand all lines: doc/src/sgml/ref/create_aggregate.sgml
+1-4Lines changed: 1 addition & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -386,10 +386,7 @@ SELECT col FROM tab ORDER BY col USING sortop LIMIT 1;
386386
If this parameter is omitted or is zero, a default estimate is used
387387
based on the <replaceable>state_data_type</replaceable>.
388388
The planner uses this value to estimate the memory required for a
389-
grouped aggregate query. The planner will consider using hash
390-
aggregation for such a query only if the hash table is estimated to fit
391-
in <xref linkend="guc-work-mem"/>; therefore, large values of this
392-
parameter discourage use of hash aggregation.
389+
grouped aggregate query.
393390
</para>
394391
</listitem>
395392
</varlistentry>

0 commit comments

Comments
0 (0)
Morty Proxy This is a proxified and sanitized view of the page, visit original site.