On sön, 2011-07-17 at 18:39 -0400, Bruce Momjian wrote:
> 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
Sounds like it would be good to document the behavior if the limit is
exceeded in each case.
In response to
pgsql-hackers by date
|Next:||From: Peter Geoghegan||Date: 2011-07-18 13:12:20|
|Subject: Reduced power consumption in autovacuum launcher process|
|Previous:||From: Pavel Golub||Date: 2011-07-18 10:38:37|
|Subject: Re: fixing PQsetvalue()|
pgsql-committers by date
|Next:||From: Tom Lane||Date: 2011-07-18 14:36:07|
|Subject: Re: Re: [COMMITTERS] pgsql: Add temp_file_limit GUC parameter to constrain temporary file sp |
|Previous:||From: Robert Haas||Date: 2011-07-18 04:50:15|
|Subject: pgsql: Create a "fast path" for acquiring weak relation locks.|