From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgreSQL(dot)org> |
Subject: | Re: [COMMITTERS] pgsql: Add temp_file_limit GUC parameter to constrain temporary file sp |
Date: | 2011-07-17 22:39:19 |
Message-ID: | 201107172239.p6HMdJX12317@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers pgsql-hackers |
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. +
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2011-07-18 00:36:49 | Re: [COMMITTERS] pgsql: Enable CHECK constraints to be declared NOT VALID |
Previous Message | Tom Lane | 2011-07-17 21:10:02 | Re: [COMMITTERS] pgsql: Add temp_file_limit GUC parameter to constrain temporary file sp |
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2011-07-17 23:29:10 | Re: proposal: a validator for configuration files |
Previous Message | Mark Kirkwood | 2011-07-17 22:11:46 | Re: Re: patch review : Add ability to constrain backend temporary file space |