On Tue, Jul 19, 2011 at 10:29:45AM +1200, Mark Kirkwood wrote:
> On 19/07/11 02:36, Tom Lane wrote:
> >Bruce Momjian<[email protected]> writes:
> >>Tom Lane wrote:
> >>>Huh? Seems like a waste of text to me. What else would happen?
> >>Well, if we exceed work_mem, we spill to temp disk. If we exceed temp
> >>disk, we error out. Those different behaviors don't seem obvious to me.
> >[ shrug... ] Feel free to change it.
> >
> >
>
> No objections from me - can't see any harm in making it very clear
> what happens when the limit is exceeded :-)
Documentation patch attached and applied, and backpatched to 9.2.
--
Bruce Momjian <[email protected]> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
diff --git a/doc/src/sgml/config.sgml b/doc/src/sgml/config.sgml
new file mode 100644
index 074afee..216c095
*** a/doc/src/sgml/config.sgml
--- b/doc/src/sgml/config.sgml
*************** SET ENABLE_SEQSCAN TO OFF;
*** 1138,1144 ****
<para>
Specifies the maximum amount of disk space that a session can use
for temporary files, such as sort and hash temporary files, or the
! storage file for a held cursor.
The value is specified in kilobytes, and <literal>-1</> (the
default) means no limit.
Only superusers can change this setting.
--- 1138,1145 ----
<para>
Specifies the maximum amount of disk space that a session can use
for temporary files, such as sort and hash temporary files, or the
! storage file for a held cursor. A transaction attempting to exceed
! this limit will be cancelled.
The value is specified in kilobytes, and <literal>-1</> (the
default) means no limit.
Only superusers can change this setting.
--
Sent via pgsql-hackers mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
