Horton
Menu

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

Mark Kirkwood <mark.kirkwood@catalyst.net.nz>

View thread
From: Mark Kirkwood <mark.kirkwood@catalyst.net.nz>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Bruce Momjian <bruce@momjian.us>, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2011-07-18T22:29:45Z
Lists: pgsql-hackers 
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 :-)

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.