mirror of
https://github.com/postgres/postgres.git
synced 2025-08-31 17:02:12 +03:00
Add temp_buffers GUC variable to allow users to determine the size
of the local buffer arena for temporary table access.
This commit is contained in:
@@ -1,5 +1,5 @@
|
||||
<!--
|
||||
$PostgreSQL: pgsql/doc/src/sgml/runtime.sgml,v 1.309 2005/03/14 06:49:48 neilc Exp $
|
||||
$PostgreSQL: pgsql/doc/src/sgml/runtime.sgml,v 1.310 2005/03/19 23:27:04 tgl Exp $
|
||||
-->
|
||||
|
||||
<chapter Id="runtime">
|
||||
@@ -1038,6 +1038,33 @@ SET ENABLE_SEQSCAN TO OFF;
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry id="guc-temp-buffers" xreflabel="temp_buffers">
|
||||
<term><varname>temp_buffers</varname> (<type>integer</type>)</term>
|
||||
<indexterm>
|
||||
<primary><varname>temp_buffers</> configuration parameter</primary>
|
||||
</indexterm>
|
||||
<listitem>
|
||||
<para>
|
||||
Sets the maximum number of temporary buffers used by each database
|
||||
session. These are session-local buffers used only for access
|
||||
to temporary tables. The default is 1000. The setting can
|
||||
be changed within individual sessions, but only up until the
|
||||
first use of temporary tables within a session; subsequent
|
||||
attempts to change the value will have no effect on that session.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
A session will allocate temporary buffers as needed up to the limit
|
||||
given by <varname>temp_buffers</>. The cost of setting a large
|
||||
value in sessions that do not actually need a lot of temporary
|
||||
buffers is only a buffer descriptor, or about 64 bytes, per
|
||||
increment in <varname>temp_buffers</>. However if a buffer is
|
||||
actually used an additional 8192 bytes will be consumed for it
|
||||
(or in general <symbol>BLCKSZ</symbol> bytes).
|
||||
</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry id="guc-work-mem" xreflabel="work_mem">
|
||||
<term><varname>work_mem</varname> (<type>integer</type>)</term>
|
||||
<indexterm>
|
||||
|
Reference in New Issue
Block a user