Horton
Menu

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

Bruce Momjian <bruce@momjian.us>

View thread
From: Bruce Momjian <bruce@momjian.us>
To: Mark Kirkwood <mark.kirkwood@catalyst.net.nz>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2012-08-03T19:15:56Z
Lists: pgsql-hackers

Attachments

On Tue, Jul 19, 2011 at 10:29:45AM +1200, Mark Kirkwood wrote:
> On 19/07/11 02:36, Tom Lane wrote:
> >Bruce Momjian<bruce@momjian.us>  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  <bruce@momjian.us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

  + It's impossible for everything to be true. +

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.