From 77a7e9968bf109d11b87c40ba41d4b1a7f1d28ea Mon Sep 17 00:00:00 2001 From: Tom Lane Date: Mon, 12 Aug 2002 00:36:12 +0000 Subject: Change memory-space accounting mechanism in tuplesort.c and tuplestore.c to make a reasonable attempt at accounting for palloc overhead, not just the requested size of each memory chunk. Since in many scenarios this will make for a significant reduction in the amount of space acquired, partially compensate by doubling the default value of SORT_MEM to 1Mb. Per discussion in pgsql-general around 9-Jun-2002.. --- doc/src/sgml/runtime.sgml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'doc/src') diff --git a/doc/src/sgml/runtime.sgml b/doc/src/sgml/runtime.sgml index 8061f74ecc2..4c2556c7817 100644 --- a/doc/src/sgml/runtime.sgml +++ b/doc/src/sgml/runtime.sgml @@ -1,5 +1,5 @@ @@ -1640,8 +1640,8 @@ dynamic_library_path = '/usr/local/lib/postgresql:/home/my_project/lib:$libdir' Specifies the amount of memory to be used by internal sorts and hashes before switching to temporary disk files. The value is - specified in kilobytes, and defaults to 512 kilobytes. Note that - for a complex query, several sorts and/or hashes might be + specified in kilobytes, and defaults to 1024 kilobytes (1MB). + Note that for a complex query, several sorts and/or hashes might be running in parallel, and each one will be allowed to use as much memory as this value specifies before it starts to put data into temporary files. Also, each running backend could be doing one -- cgit v1.2.3