Horton
Menu

Re: Re: [COMMITTERS] pgsql: Add temp_file_limit GUC parameter to constrain temporary file sp

Peter Eisentraut <peter_e@gmx.net>

View thread
From: Peter Eisentraut <peter_e@gmx.net>
To: Bruce Momjian <bruce@momjian.us>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, PostgreSQL-development <pgsql-hackers@postgreSQL.org>
Date: 2011-07-18T10:52:50Z
Lists: pgsql-hackers 
On sön, 2011-07-17 at 18:39 -0400, Bruce Momjian wrote:
> Tom Lane wrote:
> > Bruce Momjian <bruce@momjian.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.

Sounds like it would be good to document the behavior if the limit is
exceeded in each case.

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Add temp_file_limit GUC parameter to constrain temporary file space usage.