Tom Lane wrote:
> Bruce Momjian <bruce(at)momjian(dot)us> writes:
> > Tom Lane wrote:
> >> Add temp_file_limit GUC parameter to constrain temporary file space usage.
> >>
> >> The limit is enforced against the total amount of temp file space used by
> >> each session.
> >>
> >> Mark Kirkwood, reviewed by C?dric Villemain and Tatsuo Ishii
>
> > Should we document that sessions that exceed this limit generate an
> > error? I don't see any mention of this in the docs.
>
> 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.
The work_mem docs do mention is spills to disk though, so maybe it is
OK.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
In response to
Responses
pgsql-hackers by date
| Next: | From: Robert Haas | Date: 2011-07-17 23:29:10 |
| Subject: Re: proposal: a validator for configuration files |
| Previous: | From: Mark Kirkwood | Date: 2011-07-17 22:11:46 |
| Subject: Re: Re: patch review : Add ability to constrain backend
temporary file space |
pgsql-committers by date
| Next: | From: Robert Haas | Date: 2011-07-18 00:36:49 |
| Subject: Re: [COMMITTERS] pgsql: Enable CHECK constraints to be
declared NOT VALID |
| Previous: | From: Tom Lane | Date: 2011-07-17 21:10:02 |
| Subject: Re: [COMMITTERS] pgsql: Add temp_file_limit GUC parameter to constrain temporary file sp |