aboutsummaryrefslogtreecommitdiff
path: root/doc/src
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2002-08-12 00:36:12 +0000
committerTom Lane <tgl@sss.pgh.pa.us>2002-08-12 00:36:12 +0000
commit77a7e9968bf109d11b87c40ba41d4b1a7f1d28ea (patch)
treee33aa3030956bcc878a3181e9cd31efad38b0d6c /doc/src
parente44beef712144316cb83d32ccf3231a1503c9655 (diff)
downloadpostgresql-77a7e9968bf109d11b87c40ba41d4b1a7f1d28ea.tar.gz
postgresql-77a7e9968bf109d11b87c40ba41d4b1a7f1d28ea.zip
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..
Diffstat (limited to 'doc/src')
-rw-r--r--doc/src/sgml/runtime.sgml6
1 files changed, 3 insertions, 3 deletions
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 @@
<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/runtime.sgml,v 1.123 2002/08/09 22:52:04 petere Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/runtime.sgml,v 1.124 2002/08/12 00:36:11 tgl Exp $
-->
<Chapter Id="runtime">
@@ -1640,8 +1640,8 @@ dynamic_library_path = '/usr/local/lib/postgresql:/home/my_project/lib:$libdir'
<para>
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